Skip to main content
Skip table of contents

Splunk SAML Integration

This document explains how to implement Monosign with Splunk. It covers Single Sign-On. Before you continue, it is better to start with Splunk’s Single Sign-On guide.

This document will cover Splunk Enterprise and Cloud solution.

📑 Instructions

This documentation contains 4 main steps for integration.

  1. Creating an Application on Monosign

  2. Configuration Single Sign-On for Splunk

  3. Assign a user to the Splunk app

  4. Sign In Test

  5. Optional Settings on Splunk

1- Creating an Application on Monosign

Create your application on Monosign and configure your access policy. Once you create, click “Keys” and add a new Access Key for SAML Key for access.

We will need this information while we configure the Splunk app.




Key Type


Rest API, OAuth 2.0, JWT, OIDC/OpenID, SAML, RADIUS, Access Gateway, LDAP, AuthN/Z Server



Lifetime or Specific Date/Time - By Default Lifetime is Enabled.

Configuration details for the Splunk application are provided as follows:

Change ACS(Assertion Consumer Url), Audience, Entity Id, NameId Format, Name Id and Group Mapping.



Assertion Consumer Url




Entity Id


NameId Format

System Default (unspecified)

Name Id


Extra Attributes

mail : {{Email}}

realName : {{Profile.FormattedName}}

Enable Group Mapping


Group Mapping Attribute


To ensure that the application has access to user groups, follow these steps:

  1. If the application hasn't been configured yet, click the “Edit” option for the application.

  2. In the application settings, navigate to the “Source, Provider, and Profile” tab.

  3. Configure the “User Access Type“ and “User Group Access Type” as “Only Assigned Users.”

Configuring this setting will allow the application to access by user groups when users sign in.




User Access Type

Defines which Users will access to this application.

Only Assigned Users
All Users

User Group Access Type

Defines application’s user group access

Only Assigned Users
Assigned Users and Defined Sources
All Users

Profile Access Type

Defines Application’s user’s profile access

Restricted - Only restricted user profile attributes
All - All user profile attributes

2- Configuration Single Sign-On for Splunk

As it highlighted at the beginning of document, please check out the Splunk’s SSO configuration page first.

Please add your SAML settings to the application. The following information is needed for your configuration. The following information is needed for your configuration file or environment file. Before configure Splunk go to application key and download IdP Metadata.

Open Splunk configure Authentication Method page under Settings.

Click SAML and SAML Settings

Click SAML Configuration

Click Select File and upload downloaded IdP Metadata file from Monosign.

Please verify below settings configured properly:



Single Sign On (SSO) URL

Single Log Out (SLO) URL

IdP certificate path


Issuer Id

Entity Id

Sign AuthnRequest


Fully qualified domain name or IP of the load balancer


Redirect port-load balancer port


SSO Binding

HTTP Redirect

Signature Algorithm


SLO Binding

HTTP Redirect

Now, go back to Monosign and give access to your users and try login.

3- Assign a user to the Splunk app

Please follow below instructions on how to assign a user to the Splunkapplication. In this example john.smith will assign to the application access.

Splunk go to Settings → Authentication Method → SAML Settings → New Group

Type same group name on the Active Directory group which assigned user is member of than give permissions.

4- Sign In Test

Now try login. Navigate to the Splunk app. Click Monosign on the UI.

If everything is well configured, you will be redirected to Monosign’s login page. You can log in passwordless with your QR code or you can type your user name and password.

When you logged, you are gonna be redirected to the Splunk as which role assigned previous steps.

If something goes wrong while trying to login to Splunk Web console with SAML, below link can be used for the local authentication

For Enterprise


For Cloud


Replace {name} with your account name

5- Optional Settings on Splunk

If the following error is encountered during the login process after Splunk SAML integration:

Login to Splunk server via ssh go to /opt/splunk/etc/system/local folder and edit authentcation.conf file. Change signedAssertion settings from true to false.




signedAssertion = false

Than restart Splunk service

/opt/splunk/bin/splunk restart

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.