Versions Compared

Key

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

This article incudes updates is new for Smart ID Identity Manager 245.0.R11.

For development - and test - environments, test keys and certificates for all default descriptors can be generated using features of the IDM bootstrap.zip package and bootstrap Docker docker container.

The bootstrap CA certificate generated by the procedure below will have a validity of 20 years, and each end-entity certificate will be valid for 1 one year.
The generated PINs for every P12 file are automatically scrambled.
No keys and certificates will be generated for descriptions which absent from signencrypt.xml.

For Tomcat

...

development or test deployment

Requirements

...

  • Tomcat not started

  • Tomcat folder containing unpacked IDM Operator and IDM Admin of IDM 24.R1 5.0.0, or later versions, on Linux or Windows

  • unpacked bootstrapping.zipfor the respective IDM release

Instructions

...

  1. Open a command-line window.

  2. Change to the unpacked bootstrap folder containing create_sign_encrypt_certs.sh (linux) or create_sign_encrypt_certs.bat (windows).

  3. Execute the respective script for your OS.

    1. Linux: ./create_sign_encrypt_certs.sh --targetDir /PATH/TO/TOMCAT/webapps/idm-operator/WEB-INF/classes [OPTIONAL ARGS]

    2. Windows: create_sign_encrypt_certs.bat --targetDir C:\PATH\TO\TOMCAT\webapps\idm-operator\WEB-INF\classes [OPTIONAL ARGS]
      Execute the script without any parameters to see all supported arguments (if you need the plain text passwords of the generated P12 files, then adding the passwordList argument is recommended):

      Code Block
      create_sign_encrypt_certs.bat / create_sign_encrypt_certs.sh

      
            --caDir <dir>           CA cert directory - absolute or relative to

      
                                    bootstrapping directory (default: cacerts)

      
            --configFile <file>     config to modify - absolute or relative to

      
                                    target directory (default:

      
                                    engineSignEncryptConfig.xml)

      
            --passwordList <file>   optionally create file which lists unscrambled

      
                                    passwords - absolute or relative to target

      
                                    directory (will overwrite existing)

      
            --targetDir <dir>       target directory for certificates - absolute

      
                                    or relative to current directory
  4. Copy all P12files and engineSignEncryptConfig.xml from idm-operator/WEB-INF/classes to idm-admin/WEB-INF/classes
    ( optionally you can prune the files and XML entries which IDM Admin does not need).

For

...

docker development or test deployment

Requirements

...

  • An unpacked smartid SmartID package for the respective IDM release on a Linux/WSL docker host

  • no No container started

Instructions

...

  1. Enter Open the smartid/docker/composefolder.

  2. Prepare the files init-smartid.env and smartid.env according to the deployment documentation.
    If you need the plain text passwords of the generated P12 files, then edit smartid/docker/compose/identitymanager/bootstrap/docker-compose.yml
    and replace
    command: ["-configFile", "/usr/local/tools/config/signencrypt.xml", "-targetDir", "/usr/local/tools/certs"]

    within the create_sign_encrypt_certs section with
    command: ["-configFile", "/usr/local/tools/config/signencrypt.xml", "-targetDir", "/usr/local/tools/certs", "-passwordList", "pwlist.txt"].
    This will ensure the file smartid/docker/compose/certs/pwlist.txt will be created.

...

Additional information

Expand
titleUseful links

...