This documentation supports the 9.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.Click here to view the documentation for a supported version of Remedy Single Sign-On.

Creating signing and encryption certificates

You must create signing and encryption certificates to use for establishing a trust relationship between the Identity Provider (IdP)—such as AD FS and LDAP—and the BMC Atrium Single Sign-On server. Generate two certificates: one for signing (example test_sig sha1) and one for encrypting (example test_enc sha1).

Note

If you plan to exchange metadata XML files from the IdP server, you do not need to import or export the signing and encryption certificates manually, because they are exchanged as a part of the SAMLv2 metadata.

To create signing and encryption certificates

  1. On the BMC Atrium SSO Admin Console, click Edit Server Configuration. The Server Configuration Editor is displayed.
  2. On the Certificates tab, select SAMLv2 KeyStore from the Certificate Store list.
  3. Click New. The New Certificate Key Pair dialog box is displayed.
  4. Enter the following parameter values:
    • Alias Name—The alias name for the generated certificate. Generally, this value is the host name for the certificate.
    • Validity Period—The number of days for which the certificate is valid. This value must be greater than 0.
    • SAN—The subject alternative names. SANs are semicolon-separated, valid, resolvable DNS host names.
  5. Click Generate.
  6. Stop and restart the BMC Atrium Single Sign-On server.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*