Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This article is valid for Smart ID Identity Manager 24.R1 or later.

Upon startup, IDM Identity Manager Operator and IDM Identity Manager Administrator will perform various checks of the Sign and Encrypt engine's configuration. Depending on the severity, failed checks will lead to log messages or even prevent the system from starting. These checks in the sections below carried out:

Check for demo certificates

...

Secrets are stored in the Secret Fields Store. If the wrong key is configured, IDM Identity Manager will not be able to decrypt existing secrets. This check makes sure that the correct key is configured.

...

This particular check is performed by IDM Identity Manager Operator only.

IDM Identity Manager  signs the history of the objects it manages. When you are using an already existing Object History chain, this check makes sure that certificates for signing and verification of this chain are properly configured in a way that allows the chain to be continued. This means that the certificate and associated keypair used for the last entry of the chain must still be available.

...

For Tomcat deployment: add the following to WEB-INF/classes/system.properties of the IDM Identity Manager Operator webapp:

Code Block
# replace NEW_CHAIN with the desired name for the replacement chain
commonHistoryService.chainName=NEW_CHAIN

...