Update the SAML metadata in Ironclad when your identity provider replaces its SAML signing certificate.
Use Case
Your organization uses SAML single sign-on (SSO) to access Ironclad. Before the certificate used by your identity provider (IdP) expires, generate a replacement certificate in the IdP and upload its updated federation metadata XML file to Ironclad. This keeps the SSO configuration current without requiring Ironclad Support to make the change.
Prerequisites
| Features |
SAML SSO configured for your Ironclad instance |
| Connected Systems |
Your identity provider (IdP), such as Okta, Microsoft Entra ID, OneLogin, or ADFS. |
| Permissions |
You must have permission to access and edit the SAML sign-on configuration in Ironclad |
Update the Certificate in Ironclad
To update your SAML signing certificate:
In your IdP, generate a replacement SAML signing certificate.
Download the updated federation metadata XML file from your IdP.
Note: You will only upload the federation metadata XML file to Ironclad. Don't send any private key material.
In Ironclad, select your profile icon, then go to Company Settings > Integrations > SAML Sign On Configuration.
Click the SAML tab.
Under IdP Configuration XML, upload the updated federation metadata XML file.
When the Identity Provider Certificate field updates, click Save.
Once your new certificate is generated, check to verify that the expiration date was updated. Then, you can activate the replacement certificate in your IdP.
Once activated, you can open up an incognito or private browsing window, and sign in to Ironclad as a test user to verify that your SSO works.