How to verify an RKM client policy?
client.applicationpolicy is always 000102030405060708091011
If you want to see what your client is allowed to do given its policy, open your application registration file and look at the client.applicationpolicy parameter. Split the entire value value into values of 2 characters, then refer to the values with the following table:
00 - Can Encrypt
01 - Can Decrypt
02 - Can do HMAC
03 - Can do HMAC Verify
04 - Can do GetKey
05 - Can do PutKey (Import key)
06 - Can Generate a key (Create key)
07 - Can change key state, create and change key attribute (update key)
08 - Can do certificate rollover
09 - Can get a certificate request
10 - Can sign
11 - Can verify
Example:
- if your application policy is 000104, your application can encrypt, can decrypt and can get a key.
- if your application policy is 000102030405060708091011, your application is allowed everything possible.
Related Articles
Unable to see quick links solution tabs or navigation menu after signing in with SSO 90Number of Views No suitable driver found when testing a PostgreSQL database collector in RSA Identity Governance & Lifecycle 554Number of Views What should I do if I found someone's lost RSA SecurID hardware token? 139Number of Views How to check/schedule MegaRAID consistency checks 37Number of Views RSA Identity Governance & Lifecycle log message "Could not find new XAResource" in server.log file 586Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide