Rotate a Signing Certificate for Custom SAML Applications in Okta
Last Updated:
Overview
Okta does not automatically replace and activate new certificates for custom Security Assertion Markup Language (SAML) applications before the old certificate expires. Okta requires a manual rollover process to prevent downtime because automatic rotation breaks the trust with the Service Provider (SP). Okta generates a notification in the Tasks section of the Okta Admin Console and via email 60 days before the expiration, prompting a manual renewal of the signing certificate.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Custom Security Assertion Markup Language (SAML) Applications
Solution
What are the steps to rotate a signing certificate for a custom SAML application?
Generate a new certificate in the Okta Admin Console, upload it to the custom application, and activate it in Okta.
- In the Okta Admin Console, go to Applications > Applications.
- Select the custom SAML application.
- Select the Sign On tab.
- Scroll to the SAML Signing Certificates section.
- Click Generate New Certificate.
- NOTE: Okta generates a new certificate with an Inactive status, while the old certificate remains Active.
- Download the new certificate or metadata.
- Upload the new certificate to the SAML settings of the custom application.
- NOTE: If the application does not support multiple certificates, perform this step during a scheduled maintenance window.
- Return to the SAML Signing Certificates section in Okta.
- Locate the new certificate.
- Click Actions and select Activate.
