LTPA Token Corruption, EPOCH Refresh

BackGround: For successful synchronization we would need a valid LTPA token, looking at the nodeagent logs it looks like the EPOCH got refreshed and synch operation is failing after, which means the LTPA token we have may have become corrupt.  

 ADMS0005E: The system is unable to generate synchronization request: javax

.management.JMRuntimeException: ADMN0022E: Access is denied for the getRepositoryEpoch operation on ConfigRepository MBean bec

ause of insufficient or empty credentials.

In Administrative console:

1.      SSL certificate and key management -> Key set groups ->Select Key set group name -> uncheck the box for "Automatically generate keys"
Make sure to clear the Automatically generate keys option

2.      From the Key set groups -> check key set Group name and hit Generated Keys tab.

3.      Click OK and Save to save the changes to the master configuration.

4.      Stop the dmgr

5.      For the DM delete 1) wstemp, 2) temp and $config/temp -> Make SURE you only delete temp and NOT config folder under DM profile root directory

6.      Start the dmgr

7.      Stop the Node using stopNode command.

8.      Manually synchronize

9.      Start Node

10.  Verify if synchronization operation again.

We may have to restart the application server JVM as well, but we cannot do that ourselves and if it comes down to it we will have to have the application group schedule a restart request when it is convenient for them to do so