Versions Compared

Old Version 28

changes.mady.by.user Ylva Andersson

Saved on

compared with

New Version 29

changes.mady.by.user Ylva Andersson

Saved on

Key

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

Comment: Potentially a new article?

Info

This article is new for Smart ID Identity Manager 24.R1.

...

  1. Import the certificates into your HSM and/or place any of the credentials which are stored in PKCS#12 files to the correct location:

    1. Tomcat on Windows: C:\PATH\TO\TOMCAT\webapps\idm-[admin|operator]\WEB-INF\classes\

    2. Tomcat on Linux: /path/to/tomcat/idm-[admin|operator]/WEB-INF/classes/

    3. Docker on Linux: /PATH/TO/smartid/docker/compose/certs/ (additionally /PATH/TO/smartid/docker/compose/cacerts/ for CA certificates that need to be trusted)

  2. Edit the XML configuration file(s) to reference the appropriate files:

    1. Tomcat on Windows: C:\PATH\TO\TOMCAT\webapps\idm-[admin|operator]\WEB-INF\classes\engineSignEncryptConfig.xml

    2. Tomcat on Linux: /path/to/tomcat/idm-[admin|operator]/WEB-INF/classes/engineSignEncryptConfig.xml

    3. Docker on Linux: /PATH/TO/smartid/docker/compose/identitymanager/config/signencrypt.xml
      Each file must be referenced by the path within the container, as opposed to the path on the host. For example: file:/certs/MYFILE.p12

  3. Import the configZipSigner certificate or its issuer into the Identity Manager truststore (place it into /PATH/TO/smartid/docker/compose/cacerts/ on Dockerdocker).