Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: renamed to new Smart ID names

For secure communication between Smart ID Identity Manager (PRIME) service providers and the identity provider, such as Smart ID Digital Access component (Hybrid Access Gateway), SSL and SAML certificates are needed. 

This article describes how to create demo certificates or extract certificates for the following use cases: 

Panel


Excerpt

SSL server certificates for https communication:

  • For Identity Manager, SSL server certificate in PKCS#12 format. 
    • Exampleprimeidm.local.p12
  • For Digital Access as identity provider, SSL server certificate and private key as PKCS#8 PEM files. 
    • Example: Certificate:  hagda.local.pemPrivate Key: hagda.local.key.pem

SAML certificates for signing and encryption:

  • For Identity Manager, SAML certificate in PKCS#12 format. 
    Example: primeidm.saml.p12
  • For Digital Access as identity provider, SAML certificate and private key as PKCS#8 PEM files.
    Example:Certificate: hagda.saml.pemPrivate Key: hagda.saml.key.pem 


For more information on how to set up SAML, see Enable two-factor authentication to Identity Manager clients via SAML federation


Expandall

SSL server certificates

For https communication, SSL server certificates are needed for Identity Manager and the identity provider. Follow the steps if you need to create (for demo use cases) or extract keys and certificates you got from a trusted PKI.

SSL server certificate for identity provider

Expand
titleCreate SSL server certificates for identity provider

For demo use cases, it is sufficient to create a self-signed certificate including private keys. 

Note

Skip these steps if a real certificate exists.

Example - Create self-signed certificate for Digital Access:

  1. Use the java keytool command to create a self-signed certificate including private keys:

    Code Block
    languagetext
    titleExample: java keytool command
    keytool -genkey -keyalg RSA -alias selfsigned -keystore hagda.local.jks -storepass <password> -validity 1080 -keysize 2048


  2. To use the server certificate with Digital Access, a key and certificate are required. Use the created jks container to transform to p12:

    Code Block
    languagetext
    titleExample: Transform to P12
    keytool -importkeystore -srckeystore hag.localda.jks -destkeystore hagda.local.p12 -deststoretype PKCS12 -srcalias selfsigned -deststorepass <password> -destkeypass <password>



Expand
titleExtract SSL server certificates for identity provider

Some identity providers, such as Digital Access, require the certificate and key in a separate file. Use the following commands if you want to extract them from the .p12 container.

Example - Extract certificate for Digital Access:

  1. Use the p12 to extract the certificate:

    Code Block
    languagetext
    titleExample: Extract certificate
    openssl pkcs12 -in hagda.local.p12 -nokeys -out hagda.local.pem


  2. Use the p12 to extract the key:

    Code Block
    languagetext
    titleExample: Extract key
    openssl pkcs12 -in hagda.local.p12 -nodes -nocerts -out key.pem


SSL server certificate for Identity Manager

Expand
titleCreate SSL server certificates for Identity Manager

For demo use cases, it is sufficient to create a self-signed certificate including private keys.  

Note

Skip these steps if a real certificate exists.

  1. Use the java keytool command to create a java keystore  (prime.localidm.jks) containing a key-pair with a corresponding self-signed certificate:

    Code Block
    titleExample: Create self-signed certificate for PRIME
    keytool -genkey -keyalg RSA -alias selfsigned -keystore primeidm.local.jks -storepass <password> -validity 1080 -keysize 2048 


  2. Use the created jks container to transform to p12:

    Code Block
    languagetext
    titleExample: Transform to P12
    keytool -importkeystore -srckeystore prime.localidm.jks -destkeystore primeidm.local.p12 -deststoretype PKCS12 -srcalias selfsigned -deststorepass <password> -destkeypass <password> 


SAML certificates

For SAML, certificates for signing and encryption are needed for each service provider and for the identity provider. Follow the steps if you need to create (for demo use cases) or extract keys and certificates you got from a trusted PKI.

SAML certificate for identity provider

Expand
titleCreate SAML certificates for identity provider

For SAML, the identity provider needs a certificate for signing and encryption. 

For demo use cases, it is sufficient to create a self-signed certificate including private keys.

Note

Skip these steps if a real certificate exists.

Example - Create SAML certificate for Digital Access:

  1. Use the java keytool command to create a self-signed certificate including private keys:

    Code Block
    languagetext
    titleExample: java keytool command
    keytool -genkey -keyalg RSA -alias selfsigned -keystore hagda.saml.jks -storepass <password> -validity 1080 -keysize 2048 


  2. To use the SAML certificate with Digital Access, a key and certificate are required. Use the created jks container to transform to p12:

    Code Block
    languagetext
    titleExample: Transform to P12
    keytool -importkeystore -srckeystore hagda.saml.jks -destkeystore hagda.saml.p12 -deststoretype PKCS12 -srcalias selfsigned -deststorepass <password> -destkeypass <password> 



Expand
titleExtract SAML certificates for identity provider

Some identity providers, such as Digital Access, require the certificate and key in a separate file. Use the following commands if you want to extract them from the .p12 container.

Example - Extract SAML certificate for Digital Access:

  1. Use the p12 to extract the certificate:

    Code Block
    languagetext
    titleExample: Extract certificate
    openssl pkcs12 -in hagda.saml.p12 -nokeys -out hagda.saml.pem 


  2. Use the p12 to extract the key:

    Code Block
    languagetext
    titleExample: Extract key
    openssl pkcs12 -in hagda.saml.p12 -nodes -nocerts -out hagda.saml.key.pem 


SAML certificates for service providers 

Expand
titleCreate SAML certificates for Identity Manager

For SAML, each service provider (tfor example, Identity Manager and Smart ID Self-Service) needs a certificate for signing and encryption.

For demo use cases, it is sufficient to create self-signed certificates including private keys. 

Note

Skip these steps if real certificates exist.

To create a certificate for Identity Manager:

  1. Use the java keytool command to create a key store with a new private key entry:

    Code Block
    languagetext
    titleExample: java keytool command
    keytool -genkeypair -alias sp -keypass <password> -keystore samlKeystore.jks 

    In this example, sp is used as alias for keys and certificate of the Identity Manager SAML certificate.

  2. Transform the proprietary jks keystore to a .p12 file:

    Code Block
    languagetext
    titleExample: Transform to PKCS#12
    keytool -importkeystore -srckeystore samlKeystore.jks -destkeystore samlKeystore.p12 -deststoretype PKCS12 -srcalias sp 
    -deststorepass <password> -destkeypass <password>