Convert to LDAP from Splunk authentication
If you move from Splunk authentication to LDAP, it's important to note that Splunk accounts are not automatically disabled and take precedence over LDAP accounts.
If you have converted from Splunk authentication system to LDAP, you might need to delete Splunk users to ensure that you're using LDAP credentials. This is only necessary if usernames are the same in both systems.
Secure local Splunk accounts
If you have configured Splunk Enterprise to use LDAP authentication, it's important to be aware that all local accounts using Splunk authentication are still present and active, including the "admin" account. You need to consider the security implications of this.
To remove all the current local accounts when enabling LDAP authentication:
- Move the
- Create a blank
- Restart Splunk Enterprise.
Keep in mind that local Splunk accounts can still be created when Splunk Enterprise is in LDAP authentication mode. Also, any local Splunk accounts that must remain for backup or disaster-recovery purposes should use a very strong password.
When using LDAP, make sure that your LDAP implementation enforces:
- Strong password requirements for length and complexity.
- A low incorrect attempt threshold for password lockout.
If your LDAP usernames are the same as the names you previously used in the built-in system (but then deleted), saved searches should work without any conversion.
If you have existing saved searches created when your system was using Splunk authentication and you'd like to transfer them to an LDAP user of a different name, edit the metadata:
$SPLUNK_HOME/etc/apps/<app_name>/metadata/local.meta and swap the
owner = <username> field under each
savedsearch permission stanza to the corresponding LDAP username and save your changes.
2. Restart Splunk Enterprise for your changes to take effect.
Test your LDAP configuration
Best practice for removing an LDAP user
This documentation applies to the following versions of Splunk Cloud Platform™: 8.1.2103, 8.2.2104, 8.2.2105 (latest FedRAMP release), 8.2.2106, 8.2.2107