Documentation > Splunk > Developing Dashboards, Views, and Apps for Splunk Web > Authentication Configuration

Developing Dashboards, Views, and Apps for Splunk Web

 


Start Here
Command Line Interface
SOAP API
Bundles
Modules
Skins
Workflow Integration
Search Language
Built-In Processors

Authentication Configuration

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Contents

Authentication Configuration

These parameters configure your authentication scheme, either LDAP or the default Splunk Authentication.


Filename

Format 

[<spec>]
attribute1 = val1
attribute2 = val2
...

Selecting an Authentication Scheme

[auth]


authType = Splunk


This sets the authentication to use, either "Splunk" or "LDAP". For Splunk Authentication, no further configuration is needed.


For more on LDAP, see the comments in the auth.conf.spec file for details. LDAP should be configured by an experienced administrator, as an incorrect configuration is likely to leave Splunk inaccessible.


Some important considerations:


The failsafe login is used when LDAP is unavailable. When you enter the plaintext failsafe password in auth.conf, the next time Splunk starts it will replace it with the encrypted password. Also, distributed live splunks uses the failsafe password because it does not have access to user credentials from LDAP.


You can configure and enable LDAP from the web interface as well. Note that when you switch authentication systems from the GUI, any users currently logged in will be logged out.


Error messages go to $SPLUNK_HOME/var/log/splunk/splunkd.log.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/2.2.3/Developer/AuthenticationConfiguration"

This documentation applies to the following versions of Splunk: 2.2 , 2.2.1 , 2.2.3 , 2.2.6 View the Article History for its revisions.


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

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!