This documentation supports the 19.08 version of Remedy Single Sign-On.

To view an earlier version, select the version from the Product version menu.

Creating and updating the SP signing certificate for SAML authentication

If you are planning to use any of the advanced SAML authentication functions described in Configuring advanced functions for SAML authentication, you must create the SP signing certificate as it is not provided out of the box. 

You create a new file or update the service provider certificate if it has expired. 

To create an SP signing certificate

  1. To generate a keystore file containing the key pair for SAML SP signing request, run the following command:

    keytool -keystore <keystorefile> -genkey -alias <aliasname> -keyalg RSA -sigalg SHA256withRSA -keysize 2048 -validity 730

    cot.jks keystore file is created. The file contains a keypair with the alias as sp-signing.

    Example:

    keytool -keystore cot.jks -genkey -alias sp-signing -keyalg RSA -sigalg SHA256withRSA -keysize 2048 -validity 730
  2. Save the generated file on the file system of a machine where the Remedy Single Sign-On server is installed.  

  3. (HA mode) Save the keystore file on each Remedy SSO server node in a cluster on the same file directory.

To update the SP certificate on the Remedy SSO server 

If your SP signing certificate has expired, perform the following tasks to update the certificate on the Remedy SSO server and at the identity provider side:

Notes

  • The paths specified in the following procedures are for Windows OS.
  • The file name of the java keystore is cot.jks.

To update the java keystore cot.jks file 

Perform the following steps on the system where the Remedy SSO server is installed.

  1. Navigate to the <tomcat>\rsso\WEB-INF\classes directory.
  2. Locate the cot.jks file and create a backup of the file.

  3. To delete the alias 'sp-signing’ from the existing cot.jks file, run the following command:

    keytool -delete -alias test2 -keystore cot.jks
  4. To create a new keypair with alias ‘test2’ in the existing cot.jks file, run the following command:

    keytool -keystore cot.jks -genkey -alias test2 -keyalg RSA -sigalg SHA256withRSA -keysize 2048 -validity 730


  5. To export ‘test2’ certificate in the PEM format, run the following command:

    keytool -export -keystore cot.jks -alias test2 -file test2.pem –rfc

    The system creates a test2.pem file.

  6. Take a backup of the updated cot.jks file.
  7. (HA mode) If you have Remedy SSO server in a cluster, replace the cot.jks file in the <tomcat>\rsso\WEB-INF\classes folder with the updated cot.jks file.

To update the signing certificate in Remedy SSO Admin Console 

  1. Log in to Remedy SSO Admin Console.
  2. Navigate to General > Advanced tab.
  3. Enter the following details:
    • Keystore File
    • Keystore Password
    • Signing Key Alias
  4. Click Save and wait for 15 seconds.
  5. Navigate to Realm, and select a realm configured for SAML authentication.
  6. On the Authentication tab, click View Metadata and verify whether the SP metadata is updated with the new signing certificate.

To update the SP metadata at the IdP side 

  1. Export the SP metadata and save it to a local file.
  2. Share the exported SP metadata and the new signing certificate with the IdP team.
  3. If you have Active Directory Federation Services (AD FS) configured as the IdP, perform the following steps to add the new signing certificate:
    1. Open Properties dialog of the relying party for Remedy SSO.
    2. Navigate to the Signature tab, and click Add.
    3. Select the new signing certificate file, and click OK.

To update the SP certificate in an HA environment

If you have Remedy SSO deployed in a high availability mode, and AD FS  configured as the IdP, to achieve a zero-down time when you update the signing certificate, perform the following steps:

  1. Shut down one Remedy SSO server instance and update the java keystore cot.jks file on it.
  2. Update the signing certificate in Remedy SSO Admin Console.
  3. Update the SP metadata at the IdP side. 

    Note

    You must not delete the old signing certificate.

  4. Make Remedy SSO server instance up again.
  5. Repeat step 1 to step 4 for all Remedy SSO server instances.
  6. After the keystore cot.jks is updated on all Remedy SSO server instances, remove the old signing certificate on Remedy SSO relying party at the AD FS side.
Was this page helpful? Yes No Submitting... Thank you

Comments