6.25 The Identity Server Becomes Inactive After Configuring a Cluster Due to Certificate Issues

After importing the Identity server in the Administration Console and configuring it to be part of a cluster, the Identity Server fails to start and becomes inactive. The system displays the following message:

Unable to read keystore : /opt/novell/devman/jcc/certs/idp/encryption.keystore

To workaround this issue:

  1. In the Administration Console, click Identity Servers > Health icon. The Services Details section shows the error message with the details of the failed keystore or truststore.

    Note the destination keystore or truststore of the failed command.

  2. Click Auditing > Troubleshooting > Certificates.

    The Certificates page displays all the keystores and truststores configured for Access Manager.

  3. Select the identified keystores or truststores, then click Re-push certificates.

    The keystore file can be Connector, Signing, Encryption, or Truststore.

    This pushes all the assigned certificates to the store. You can re-push certificates multiple times without causing any problems.

    The Identity Server restarts automatically. The Identity Server should be running after restart.