Question
Capgemini
SE
Last activity: 14 Oct 2020 11:59 EDT
Could not get CDK from systemKeyManagementCache and not able to login to pega
We are running Pega 8.4 which was upgraded a month from 8.2.1. The system was running fine until we restarted it today. After restart no operator was able to login. In the logs it was throwing error.
2020-08-14 19:03:08,111 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR Proprietary information hidden| Proprietary information hidden kumam - Could not get CDK from systemKeyManagementCache 2020-08-14 19:03:08,111 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR Proprietary information hidden| Proprietary information hidden kumam - System CDK is null 2020-08-14 19:03:08,127 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (o.dataencryption.CryptoHandler) ERROR Proprietary information hidden| Proprietary information hidden kumam - Failed to initialize Cipher :
We saw a similar issue and resolution in the communication post but it does not provide how to execute it.
We are running Pega 8.4 which was upgraded a month from 8.2.1. The system was running fine until we restarted it today. After restart no operator was able to login. In the logs it was throwing error.
2020-08-14 19:03:08,111 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR Proprietary information hidden| Proprietary information hidden kumam - Could not get CDK from systemKeyManagementCache 2020-08-14 19:03:08,111 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (dataencryption.DataKeyProvider) ERROR Proprietary information hidden| Proprietary information hidden kumam - System CDK is null 2020-08-14 19:03:08,127 INFO [stdout] (Log4j2-TF-4-AsyncLoggerConfig-1) 2020-08-14 19:03:08,111 [ default task-34] [ STANDARD] [ ] [CommonLogin:01.01.01] (o.dataencryption.CryptoHandler) ERROR Proprietary information hidden| Proprietary information hidden kumam - Failed to initialize Cipher :
We saw a similar issue and resolution in the communication post but it does not provide how to execute it.
When we restore the system to a week before DB backup, it runs fine. But restoring any backup after it is not helping. Something happened within last week but it didn't appear until we restarted it.
Please help us on it, its urgent and is stopping completely the development.
DLL Group
NL
I have raised an SR for the observed behavior running Pega 8.2.1 on Windows with a SQL Server database. The resolution that Pega gave worked for me but seems to be specific for environments with SQL server environments. I was able to successfully solve the problem. I did not take a full DB backup but made a copy of the table before truncating the original one.
Root cause description:
This is an issue specific to the MS SQL Server database when there were 6 or more CDKs in the database: CDK keys are loaded from database into Cache using an SQL statement which had the ORDER clause. By default, the ORDER clause treats NULL values differently on different databases, and this caused MS SQL databases to not load a necessary CDK key.
Solution type: Local Change Solution description: First of all please check how many keys are there in the table. To do that you should connect to your DB and on pegadata schema run query: select * from pegadata.pr_data_admin_sec_sde_cdk; Most probably there will be 6 or more entires there. To fix the problem please create copy ot that table or full database backup and shutdown all node(s) and run below query: TRUNCATE TABLE pegadata.pr_data_admin_sec_sde_cdk; then please start application and try to connect.
Please note that backup is very important in case of any issues.We have fixed the query on a product side in following versions: 8.2.8 (planned for end of October), 8.3.3(released) and 8.4.2(released)