Configuring PingAccess to use Amazon Key Management Services
During initial startup, PingAccess automatically generates a randomized master key, which by default is not encrypted. If you are running in Amazon Web Services (AWS), you can configure PingAccess to use Amazon Key Management Services (KMS) to encrypt the master key.
Before you begin
-
Make sure that you have an active connection to AWS.
-
Use AWS KMS to generate a key to use for the PingAccess master key encryption.
|
For more information about managing access rights to your keys using key policies or AWS Identity and Access Management (IAM), see AWS Key Management Service. |
About this task
To configure the encryption of the PingAccess master key, modify the pa.jwk.properties file found in <PA_HOME>/conf.
Steps
-
Stop PingAccess.
-
In a text editor, open
<PA_HOME>/conf/pa.jwk.properties. -
Locate the
pa.hostkey.masterKeyEncryptorproperty . -
Enable master key encryption.
-
Change
com.pingidentity.pa.crypto.NoOpMasterKeyEncryptorto the AWS KMS master key encryptor class namecom.pingidentity.pingcommons.aws.key.AwsKmsMasterKeyEncryptor. -
Locate the ID for the key that you generated using AWS KMS.
-
If this is not the first time starting PingAccess, prefix the key ID with
“ENCRYPT:”.Example:
After making changes, the properties file should look similar to the following:
pa.hostkey.masterKeyEncryptor=com.pingidentity.pingcommons.aws.key.AwsKmsMasterKeyEncryptor pa.hostkey.keyId=ENCRYPT:d4e6adab-e20c-4339-ba76-e4cb1348713f
-
-
Save and close the updated
pa.jwk.propertiesfile. -
Restart PingAccess.
The PingAccess master file
pa.jwkis encrypted using Amazon KMS.