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
event explorer terminated immediately once you start and you see error UnsupportedEncodingException when running adjustHe… 13Number of Views Cannot See Rules in the Admin Console Rules List of RSA Web Threat Detection 11Number of Views How to see a list of pending changes to Roles in RSA Identity Governance & Lifecycle 24Number of Views RSA Via Lifecycle & Governance administrators do not see Privileges tab for users 27Number of Views AAH Client can not see a new FI loaded to their region 13Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle