Unable to login to the Splunk with their SAML user

Available Languages

Updated:September 29, 2026
Document ID:SPLK045687

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise Splunk Cloud

Description

Unable to login to the cloud instance. After navigating to the cloud instance URL they can see the regular log inflow including 2FA but observing the below error message. 
ERROR UiSAML [12106 webui] - Verification of SAML assertion using the IDP's certificate provided failed. Error: failed to verify signature with cert


 

Investigation

Verified that certificate is expired with below command.

/etc/auth/idpCerts$ openssl x509 -in idpCert.pem -noout -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
40:8f:5d:41:fc:9d:ab:bc:49:29:4d:02:f1:8d:9a:cf
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=Microsoft Azure Federated SSO Certificate
Validity
Not Before: Apr 11 04:12:43 2019 GMT
Not After : Apr 11 04:12:43 2022 GMT


 


Resolution

Update the IDP cert as a native user with below steps.

1. Copy-paste BASE64 encoded cert into "IDP certificate chains"
This can be done from the UI Settings > Access controls -> Authentication method -> saml settings -> configure SAML > IdP certificate chains

2. Save

3. Reload authentication

Above steps can be performed by native user even though SAML user can not login.

Configure SSO Azure AD and ADFS

SAML assertion using the IDPs certificate provided failed Error

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles