- Created by Karolin Hemmingsson (Unlicensed), last modified on Jul 08, 2020
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
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:
SSL server certificates for https communication:
- For Identity Manager, SSL server certificate in PKCS#12 format.
- Example: prime.local.p12
- For Digital Access as identity provider, SSL server certificate and private key as PKCS#8 PEM files.
- Example: Certificate: hag.local.pem, Private Key: hag.local.key.pem
SAML certificates for signing and encryption:
- For Identity Manager, SAML certificate in PKCS#12 format.
Example: prime.saml.p12 - For Digital Access as identity provider, SAML certificate and private key as PKCS#8 PEM files.
Example:Certificate: hag.saml.pem, Private Key: hag.saml.key.pem
For more information on how to set up SAML, see Enable two-factor authentication to Identity Manager clients via SAML federation.
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
For demo use cases, it is sufficient to create a self-signed certificate including private keys.
Skip these steps if a real certificate exists.
Example - Create self-signed certificate for Digital Access:
Use the java keytool command to create a self-signed certificate including private keys:
Example: java keytool commandkeytool -genkey -keyalg RSA -alias selfsigned -keystore hag.local.jks -storepass <password> -validity 1080 -keysize 2048
To use the server certificate with Digital Access, a key and certificate are required. Use the created jks container to transform to p12:
Example: Transform to P12keytool -importkeystore -srckeystore hag.local.jks -destkeystore hag.local.p12 -deststoretype PKCS12 -srcalias selfsigned -deststorepass <password> -destkeypass <password>
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:
Use the p12 to extract the certificate:
Example: Extract certificateopenssl pkcs12 -in hag.local.p12 -nokeys -out hag.local.pem
Use the p12 to extract the key:
Example: Extract keyopenssl pkcs12 -in hag.local.p12 -nodes -nocerts -out key.pem
SSL server certificate for Identity Manager
For demo use cases, it is sufficient to create a self-signed certificate including private keys.
Skip these steps if a real certificate exists.
Use the java keytool command to create a java keystore (
prime.local.jks
) containing a key-pair with a corresponding self-signed certificate:Example: Create self-signed certificate for PRIMEkeytool -genkey -keyalg RSA -alias selfsigned -keystore prime.local.jks -storepass <password> -validity 1080 -keysize 2048
Use the created jks container to transform to p12:
Example: Transform to P12keytool -importkeystore -srckeystore prime.local.jks -destkeystore prime.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
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.
Skip these steps if a real certificate exists.
Example - Create SAML certificate for Digital Access:
Use the java keytool command to create a self-signed certificate including private keys:
Example: java keytool commandkeytool -genkey -keyalg RSA -alias selfsigned -keystore hag.saml.jks -storepass <password> -validity 1080 -keysize 2048
To use the SAML certificate with Digital Access, a key and certificate are required. Use the created jks container to transform to p12:
Example: Transform to P12keytool -importkeystore -srckeystore hag.saml.jks -destkeystore hag.saml.p12 -deststoretype PKCS12 -srcalias selfsigned -deststorepass <password> -destkeypass <password>
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:
Use the p12 to extract the certificate:
Example: Extract certificateopenssl pkcs12 -in hag.saml.p12 -nokeys -out hag.saml.pem
Use the p12 to extract the key:
Example: Extract keyopenssl pkcs12 -in hag.saml.p12 -nodes -nocerts -out hag.saml.key.pem
SAML certificates for service providers
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.
Skip these steps if real certificates exist.
To create a certificate for Identity Manager:
Use the java keytool command to create a key store with a new private key entry:
Example: java keytool commandkeytool -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.Transform the proprietary jks keystore to a .p12 file:
Example: Transform to PKCS#12keytool -importkeystore -srckeystore samlKeystore.jks -destkeystore samlKeystore.p12 -deststoretype PKCS12 -srcalias sp -deststorepass <password> -destkeypass <password>
- No labels