| CARVIEW |
Securing Splunk Enterprise
- Install Splunk Enterprise securely
- Secure your admin account
- About TLS encryption and cipher suites
- Securing Splunk Enterprise with FIPS
- About default certificate authentication
- Secure Splunk Enterprise on your network
- Disable unnecessary Splunk Enterprise components
- Secure Splunk Enterprise service accounts
- Deploy secure passwords across multiple servers
- Harden the network port that App Key Value Store uses
- Some best practices for your servers and operating system
- Use access control to secure Splunk data
- About user authentication
- About configuring role-based user access
- About defining roles with capabilities
- Add and edit roles with Splunk Web
- Add and edit roles with authorize.conf
- Configure access to manager consoles and apps in Splunk Enterprise
- Find existing users and roles
- Delete all user accounts
- Secure access for Splunk knowledge objects
- Use network access control lists to protect your deployment
- Set up user authentication with LDAP
- Manage Splunk user roles with LDAP
- LDAP prerequisites and considerations
- Secure LDAP authentication with transport layer security (TLS) certificates
- How the Splunk platform works with multiple LDAP servers for authentication
- Configure LDAP with Splunk Web
- Map LDAP groups to Splunk roles in Splunk Web
- Configure LDAP with the configuration file
- Map LDAP groups and users to Splunk roles using configuration files
- Test your LDAP configuration on Splunk Enterprise
- Change authentication schemes from native to LDAP on Splunk Enterprise
- Remove an LDAP user safely on Splunk Enterprise
- Configure single sign-on with SAML
- Configure SSO with PingIdentity as your SAML identity provider
- Configure SSO with Okta as your identity provider
- Configure SSO with Microsoft Azure AD or AD FS as your Identity Provider
- Configure SSO with OneLogin as your identity provider
- Configure SSO with Optimal as your identity provider
- Configure SSO in Computer Associates (CA) SiteMinder
- Secure SSO with TLS certificates
- Configuring SAML in a search head cluster
- Configure Ping Identity with leaf or intermediate SSL certificate chains
- Configure SAML SSO for other IdPs
- Configure advanced settings for SSO
- Map groups on a SAML identity provider to Splunk roles
- Modify or remove role mappings
- Configure SAML SSO in the configuration files
- Troubleshoot SAML SSO
- How to creaate Splunk authentication with CAC / Sm...
- Search Head Cluster: How to properly implement LDA...
- How to migrate from LDAP authentication to Microso...
- User Status Detection in Splunk React App with LDA...
- LDAP Authentication, single group with multiple st...
- set up LDAP user authentication
- Splunk CAC Based Authentication
- LDAP queries (not authentication) via Splunk (look...
- Unable to authenticate users in active directory
- Account lockout when using LDAP authentication for...
Set up user authentication with LDAP
Splunk Enterprise supports three types of authentication systems:
- Splunk authentication described in "Set up user authentication with Splunk's built-in system."
- LDAP, described in the topic you're now reading.
- A scripted authentication API for use with an external authentication system, such as PAM or RADIUS, described in "Set up user authentication with external systems."
About configuring LDAP authentication for Splunk Enterprise
Splunk Enterprise allows user and role configuration for LDAP users and groups. You can configure one or many LDAP servers and map users and user groups from your servers to Splunk roles.
For more information about configuring multiple LDAP servers, see "How Splunk works with multiple LDAP servers."
Before you configure LDAP, take a look at "LDAP prerequisites and considerations."
How to configure LDAP authentication
These are the main steps to configure Splunk Enterprise to work with LDAP:
1. Configure one or more LDAP strategies (typically, you configure one strategy per LDAP server).
2. Map your LDAP groups to one or more Splunk roles.
3. If you have multiple LDAP servers, specify the connection order of their servers.
You can perform these steps in Splunk Web or by editing the configuration file. See "Configure LDAP with Splunk Web" or "Configure LDAP with the configuration file" for more information.
Authentication precedence
Splunk authentication takes precedence over any external systems. This is the order in which Splunk Enterprise authenticates a user:
1. Splunk authentication
2. LDAP or scripted authentication, if one of these methods is enabled. For more information about scripted authentication see "Set up user authentication with external systems."
Answers
Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has around LDAP authentication with Splunk.
| Configure users with the CLI | Manage Splunk user roles with LDAP |
This documentation applies to the following versions of Splunk® Enterprise: 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.0.13
Comments
Download manual
Set up user authentication with LDAP
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.
Your Comment Has Been Posted Above
Feedback submitted, thanks!