Versions Compared

Old Version 18

changes.mady.by.user Josefin Klang (Deactivated)

Saved on

compared with

New Version 19

changes.mady.by.user Josefin Klang (Deactivated)

Saved on

Key

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

Comment: 24.R1 - updates throughout the entire article.

Remember to update the release version number before publishing externally.

Info

This article includes updates for Smart ID 24.R1.

...

  1. Stop the Identity Manager applications and shut down Tomcat or the respective docker containers by running docker compose downfrom within docker/compose/identitymanager/<webappname>/.

  2. Create a backup of the respective databases.

...

Set up Identity Manager to use the new keypair

  1. Open the files file for editing.
    For docker: Open docker/compose/identitymanager/config/signencrypt.xml.
    For WAR file deployment: Open WEB-INF/classes/engineSignEncryptConfig.xml in Identity Manager Operator, Identity Manager Admin, and Identity Manager Tenant.

  2. Change the attributes of the EncryptedFields descriptor and its referenced key to the values needed for the new keypair, as you set them for the NewEncryptedFields descriptor in the migration application. Note that the The descriptor's name must still be EncryptedFields and not NewEncryptedFields for Identity Manager.

  3. For docker: Rundocker compose up from within  docker/compose/identitymanager/<webappname>/ for all Identity Manager applications (Admin, Operator, and Tenant) to recreate the docker containers.
    For WAR file deployment: Start Identity Manager.