Splunk® Enterprise

Securing Splunk Enterprise

Download manual as PDF

Download topic as PDF

Configure single sign-on with SAML

You can configure Splunk software to use SAML authentication for single sign-on (SSO), using information provided by your supported identity provider (IdP).

Splunk software always outputs usernames in lowercase. If your IdP expects Splunk software to preserve uppercase letters in usernames, you can change the username to lowercase in the IdP or configure the IdP to accept the lowercase version of a username.

Note that if the search head is restarted, you must re-enter your credentials to access saved searches.


  • Either:
    • A running version of Splunk software OR
    • A managed deployment of Splunk Cloud. Self-service deployments of Splunk Cloud log in through the Splunk customer portal and cannot independently configure SAML SSO.
  • An identity provider configured to provide the role, realName, and mail attributes. The supported identity providers are:
    • Ping Identity
    • Okta
    • Azure AD
    • AD FS
    • OneLogin
    • Optimal
    • CA siteminder
  • An admin role (Splunk Enterprise) or sc_admin role (Splunk Cloud) with the change_authentication capability. This permission level lets you enable SAML and edit authentication settings on the Splunk search head.

Other IdPs

Any SAML IdP that is v2 compliant should be configurable, including the following tested IdPs. For assistance with any IdP that is not documented in this chapter, contact Support:

  • SecureAuth
  • Novell Directory
  • G Suite (Formerly Google Apps for Business)

Configure SAML to work with your IdP

SAML does not support encryption, regardless of IdP.

1. Configure SAML SSO with:

2. Map SAML groups to Splunk Enterprise roles.

Configure Duo multifactor authentication for Splunk Enterprise in the configuration file
Configure SSO with PingIdentity as your identity provider

This documentation applies to the following versions of Splunk® Enterprise: 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.3.0, 7.3.1, 7.3.2, 8.0.0

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters