Configure a Splunk Enterprise password policy using the Authentication.conf configuration file
On Splunk Enterprise only, the
authentication.conf file lets you create a password policy for users of your Splunk platform instance or deployment. Password policies set standards and minimum requirements for password complexity. The authentication.conf file is not applicable to Splunk Cloud, as you cannot configure the file on Splunk Cloud instances. Instead, use Splunk Web to configure passwords.
The policy you create with the file works with the native authentication scheme for Splunk Enterprise only. Password policies do not apply when you configure the instance to use the Lightweight Directory Access Protocol (LDAP) or Security Assertion Markup Language (SAML) authentication schemes.
Procedure for creating a password policy using configuration files
- Using a text editor, open the $SPLUNK_HOME/etc/system/local/authentication.conf file or editing.
- Make edits to the
[splunk_auth]section of the file to set the password policy, using information in the table that follows this procedure.
- Save the file and close it.
- Restart Splunk Enterprise. The password policy comes into effect immediately.
The following table describes the details of each setting:
|Specify the minimum ASCII-based alphanumeric or special characters required when a user creates a new password. Splunk Enterprise supports values between 1 and 256 characters.
|At least 8 characters
|The number of uppercase letters required for user passwords.
|At least one uppercase letter
|Zero uppercase characters
|The number of lowercase letters required for user passwords.
|At least one lowercase letter
|Zero lowercase characters
|The number of special characters required for user passwords. When this setting is populated, a user can enter any special character except a semicolon.
|At least one special character
|Zero special characters
|The number of numeric characters required for user passwords. Value can be 0 through the length of the password. The total allowed length of the password is 256. Do not create a password comprised of only number.
|At least one number
|The number of days before the password expires. Allowed values are 0 to 3650 days.
|The number of days in advance of password expiration that Splunk software issues user alerts. Allowed values are 0 to 120 days.
|Set to true to enable password expiration.
|Set to true to force users to change a weak password the next time they log in.
|Specifies whether the system locks users out after a number of failed login attempts. When this setting is enabled, user lockout is local to each search head peer in a search cluster configuration and is not replicated to other peers.
|The number of minutes that a user must wait before attempting to log in again after a lockout. The user is locked out after entering an incorrect password more times than specified in the
lockoutAttempts value in the
lockoutThresholdMins setting. Supported values are 1 - 1440 minutes.
When this setting is enabled on members of a search head cluster, user lockout is applied to individual members, not the entire cluster.
|At least 30 minutes
|The number of unsuccessful logins a user can attempt before they are locked out. The unsuccessful login attempts must occur within
lockoutThresholdMins minutes. Supported values are 1 - 64 login attempts.
When enabled on members of a search head cluster, user lockout is applied to the single search head peer, the rest of the cluster is unaffected.
|At least 5 attempts
|The number of minutes that must pass from the time of the first failed login before the failed login attempt counter resets. Supported values are 1 - 120 minutes.
When this setting is enabled on members of a search head cluster, user lockout is applied to the single search head peer, the rest of the cluster is unaffected.
|At least 5 minutes
|Set to true to keep a user's password history. If you disable this value and and enable it later, previously saved password history is preserved. Delete
$SPLUNK_HOME/etc/opasswd to remove the password history.
|The number of passwords that are stored in history. If you enable password history and provide a number such as 25, then the user is not able to reuse their previous 25 passwords. Supported values are 1 - 128 stored passwords.
|24 stored passwords
|24 stored passwords
Configure Splunk password policies
Password best practices for users
This documentation applies to the following versions of Splunk Cloud Platform™: 9.1.2312, 8.2.2202, 8.2.2112, 8.2.2201, 8.2.2203, 9.0.2205, 9.0.2208, 9.0.2209, 9.0.2303, 9.0.2305 (latest FedRAMP release), 9.1.2308