Configure SSO with OneLogin as your identity provider

If you use OneLogin as your Identity Provider (IdP), follow these instructions to configure the Splunk platform for single sign-on.

After you configure the Splunk platform for SSO, you can map groups form the IdP to those roles so that users can log in. See Map groups on a SAML identity provider to Splunk user roles so that users in those groups can log in.

For information about configuring OneLogin as an IdP, consult your OneLogin documentation.

Considerations for configuring the Splunk platform to use OneLogin as an identity provider

• An error in configuring SAML can result in users being locked out of Splunk Cloud Platform. Use the following link to access the local login using native authentication if you are locked out. In the link, replace <name> with your account name:

  https://<name>.splunkcloud.com/en-US/account/login?loginType=splunk

Configure the Splunk platform to use SAML

1. Verify that your system meets all of the requirements. See Configure single sign-on with SAML.
2. In the Settings' menu, select Authentication methods
3. Select SAML as your authentication type.
4. Click Configure Splunk to use SAML.
5. On the SAML Groups page, click SAML Configuration.
6. Download or browse and select your metadata file, or copy and paste your metadata directly into the text window. Refer to your IdP's documentation if you are not sure how to get your metadata file.
7. In General Settings, provide the following information.

   Single Sign on URL.	This field is populated automatically by your selected metadata file. It is the protected endpoint on your IdP to which the Splunk platform sends authentication requests. To access the login page once SAML is enabled, append the full login URL (/account/login) with loginType=Splunk. Users can also log into their local Splunk account by navigating directly to – splunkweb:port/en-US/account/login?loginType=Splunk
   Single Log Out URL.	OneLogin supports redirect binding for single log out. Set the binding to 'HTTPRedirect'.
   IdP's certificate path	This value can be a directory or a file, depending on your IdP requirements. If you provide a file, Splunk uses that file to validate authenticity of SAML response. If you provide a directory, Splunk looks for all the certificates that are present as children of the directory and tries to validate SAML response with each one of them, if Splunk fails to validate authenticity with all of them, response is not considered authentic.
   IdP certificate chains	If you use a certificate chain, order them as follows: 1. Root 2. Intermediate 3. Leaf
   Replicate certificates	Check this to replicate your IdP certificates in a search head cluster. When configuring SAML on a search head cluster, you must use the same certificate for each search head.
   Issuer Id	This is the Entity Id of the IdP. See your IdP documentation if you are not sure where to find this information.
   Entity ID.	This field is the entity ID as configured in the SP connection entry in your IdP.
   Sign AuthRequest.	ISet this value to false.
   Sign SAML Response.	Set this value to false.

8. Skip the Attribute Query section.
9. In the Alias section optionally provide the following aliasing information:

   Role Alias	Use this field to specify a new attribute name on any IdP and then configure an alias in your Splunk deployment for any of the three attributes.
   Real Name Alias	You may skip this field. For ADFS you can use the displayname for the Attribute Alias Real Name.
   Mail Alias	Skip this field.

10. Populate the advanced section only if you need to set up load balancing or change the SAML binding. See Configure load balancing or SAML bindings
11. Click Save.

Next step

Map SAML groups to Splunk Enterprise roles