[[_password-policies]]

=== Password Policies

When {project_name} creates a realm, it does not associate password policies with the realm. You can set a simple password with no restrictions on its length, security, or complexity. Simple passwords are unacceptable in production environments. {project_name} has a set of password policies available through the Admin Console.

.Procedure
. Click *Authentication* in the menu.
. Click the *Password Policy* tab.
. Select the policy to add in the *Add policy* drop-down box.
. Enter a value for the *Policy Value* corresponding with the policy chosen.
. Click *Save*.
+
Password Policy
image:{project_images}/password-policy.png[Password Policy]

After saving the policy, {project_name} enforces the policy for new users and sets an Update Password action for existing users to ensure they change their password the next time they log in. For example:

.Failed Password Policy
image:{project_images}/failed-password-policy.png[Failed Password Policy]

==== Password Policy Types

ifeval::[{project_community}==true]

===== HashAlgorithm

Passwords are not stored in cleartext. Before storage or validation, {project_name} hashes passwords using standard hashing algorithms. PBKDF2 is the only built-in and default algorithm available. See the link:{developerguide_link}[{developerguide_name}] on how to add your own hashing algorithm.

[NOTE]
====
If you change the hashing algorithm, password hashes in storage will not change until the user logs in.
====

endif::[]

ifeval::[{project_product}==true]
===== Hashing Algorithm

Passwords are not stored in clear text. Before storage or validation, {project_name} hashes passwords using standard hashing algorithms {project_name} that support the PBKDF2, PBKDF2-SHA256 and PBKDF-SHA512 hashing algorithms.

endif::[]

===== Hashing Iterations
Specifies the number of times {project_name} hashes passwords before storage or verification. The default value is 27,500.

{project_name} hashes passwords to ensure that hostile actors with access to the password database cannot read passwords through reverse engineering.

[NOTE]
====
A high hashing iteration value can impact performance as it requires higher CPU power.
====

===== Digits

The number of numerical digits required in the password string.

===== Lowercase Characters

The number of lower case letters required in the password string.

===== Uppercase Characters

The number of upper case letters required in the password string.

===== Special Characters

The number of special characters required in the password string.

===== Not Username

The password cannot be the same as the username.

===== Not Email

The password cannot be the same as the email address of the user.

===== Regular Expression

Password must match one or more defined regular expression patterns.

===== Expire Password

The number of days the password is valid. When the number of days has expired, the user must change their password.

===== Not Recently Used

Password cannot be already used by the user. {project_name} stores a history of used passwords. The number of old passwords stored is configurable in {project_name}.

===== Password Blacklist
Password must not be in a blacklist file.

* Blacklist files are UTF-8 plain-text files with Unix line endings. Every line represents a blacklisted password.
* {project_name} compares passwords in a case-insensitive manner. All passwords in the blacklist must be lowercase.
* The value of the blacklist file must be the name of the blacklist file.
* Blacklist files resolve against `${jboss.server.data.dir}/password-blacklists/` by default. Customize this path using:
** The `keycloak.password.blacklists.path` property.
** The `blacklistsPath` property of the `passwordBlacklist` policy SPI configuration.