Question
BNZ
NZ
Last activity: 25 Sep 2019 8:15 EDT
AWS KMS security token Exception during E-mail account configuration
I’m trying to configure the Default email account in our client PEGA cloud environment for report scheduling purposes. However, during this setup PEGA is using an AWS KMS key store that is available in the system to encrypt the email password with Encode function that is available in the Pega-RULES: Default library
At this point, I’m getting an exception from AWS saying that the security token is invalid. I tested the AWS key store file available in the system and the connectivity is fine. Does anybody know when we might encounter this exception?
Attaching the screenshots that has the exception and detailed rule invocation stack trace.
***Edited by Moderator Marissa to update platform capability tags****
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
Since the user doesn't have the old master key details, suggested with below changes and made the environment to the initial installation stage which uses the OOTB encryption.
delete from data.pr_data_admin_sec_de_key;
delete from data.pr_data_admin_sec_de_cdk where pycdkid=1;
Pegasystems Inc.
US
Can you attach your Email Account rule form? I thought this is all client specific, independent of Pegacloud env itself.
BNZ
NZ
I've attached the document that has the screenshots and mentioned the rule where we are getting the exception.
After going through the Exception stack trace, here is my analysis which could help us to resolve this.
1. Application tried to encrypt the password with the help of Keystore that is available in the Amazon KMS location.
2. It tried to call the AWSKMS service.
3. AWSKMS service returned that the request call was made from an Unrecognized client, thus returning UnrecognizedClientException.
I’m not entirely sure but the below article says that this might happen if there is an inconsistent date and time between the server (Pega Cloud) & Amazon KMS server (AWSKMS service)
https://aws.amazon.com/premiumsupport/knowledge-center/security-token-expired/
https://github.com/awslabs/amazon-kinesis-scaling-utils/issues/5
Also, I’m pretty sure that the Access/Secret key pair are valid as the connectivity looks good (refer to the document).
BNZ
NZ
Here is the Exception trace that tells us how pega invoked AWSKMS client to access the keystore.
Here is the Exception trace that tells us how pega invoked AWSKMS client to access the keystore.
BNZ
NZ
I got the comprehensive exception stack trace from the log file. If Tracer log file can be helpful, I can create a SR and send it over my support portal.
Pegasystems Inc.
US
Hi Naveen,
Please go ahead with SR creation and this will be handled by appropriate team from Pega GCS.
Thanks for all the details and please attach them to the SR.
BNZ
NZ
SR-D8285 is raised for the GCS team to help us in resolving this issue.
BNZ
NZ
Hi,
Did anyone faced this issue before. The KMS keys are configured properly in our system and they are working fine with other features(Sending data to Amazon S3 bucket).
The only time we are facing this issue is when we try to update the password in the email account rule.
Regards,
Naveen.
Accepted Solution
Pegasystems Inc.
IN
Since the user doesn't have the old master key details, suggested with below changes and made the environment to the initial installation stage which uses the OOTB encryption.
delete from data.pr_data_admin_sec_de_key;
delete from data.pr_data_admin_sec_de_cdk where pycdkid=1;