Documentation > Splunk > Admin Manual > Set up user authentication with Splunk

Admin Manual

 


Welcome
What to do first
Start Splunk
Meet Splunk Web and Splunk Apps
Before you configure
Add data and configure inputs
Indexing and event processing
Timestamps
Add and manage users
Manage indexes
Define alerts
Set up backups and retention policies
Configure data security
Set up forwarding and receiving
Deploy to other Splunk instances
Set up distributed search
Manage search jobs
Use Splunk's command line interface (CLI)
Configuration file reference
Troubleshooting

Set up user authentication with Splunk

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

Set up user authentication with Splunk

Splunk ships with support for these types of authentication systems:

Splunk with an Enterprise license comes with Splunk's built-in authentication enabled by default. Splunk's authentication allows you to add users, assign them to roles, and give those roles custom permissions as needed for your organization. Splunk's built-in system always takes precedence over any external systems, including LDAP.

If your enterprise uses LDAP and you'd like to use the users and groups defined there instead of using Splunk's authentication system, look here for information. To use scripted authentication to connect with a system such as PAM or RADIUS, see this topic.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/4.0.1/Admin/SetupuserauthenticationwithSplunk"

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 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!