To ensure uninterrupted Single Sign-On (SSO) access, SAML security certificates for Splunk Cloud must be replaced prior to their expiration date. Certificate renewal is achieved through one of two primary methods:

Please note that both Splunk Cloud and the IdP must simultaneously posses the same certs in order to use SAML authentication for logins. Find below the two different ways in which you can renew the certificates.
SAML authentication requires that both Splunk Cloud and the Identity Provider (IdP) utilise identical certificates. The following methods are available for certificate renewal:
To provide your IDP the new metada file after renewal of Splunk-provided certificate on your Search Head, follow these steps:



Alternatively, the IdP may provide new certificates to Splunk Cloud. In this scenario, the renewed certificate must be uploaded to Splunk Cloud while logged in with a native or local account.


Notes:
Expiring SAML identity provider certificates must be refreshed individually on each search head using the Reload authentication configuration button. In a SHC environment this task must be done on each member of the SHC individually.
For example, certificates on the Ad-hoc search head and the Enterprise Security search head require separate updates, as they do not synchronize automatically between these instances.
Refresh expiring SAML identity provider certificates
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
30-Sep-2026
|
Initial Release |