Skip to main content

Password hashes

authentik uses Django's encoded password format for local passwords. Importing a hash sets only the local verifier; it cannot update LDAP or Kerberos because authentik does not receive the raw password.

Generate a password hash​

Run hash_password with the target authentik version so that its work factors and salt entropy match the bundled Django configuration. Use the complete output.

docker compose run --rm server hash_password

For non-interactive use:

printf '%s\n' "$PASSWORD" | docker compose run --rm -T server hash_password

Password hash import settings​

Bootstrap imports and API imports without an override accept pbkdf2_sha256, argon2, bcrypt_sha256, and scrypt. Parameters and salt entropy must match the target authentik version's bundled Django configuration.

Django estimates salt entropy as length * log2(62). A salt generated with a different alphabet can therefore be rejected even when its actual entropy is sufficient.

These settings do not affect stored hashes; supported legacy hashes such as pbkdf2_sha1 continue to verify.

Import paths​

  • AUTHENTIK_BOOTSTRAP_PASSWORD_HASH applies these settings during the first startup and has no override. A rejected hash stops initial setup.
  • The set_password_hash API endpoint applies these settings by default. override=true accepts any configured hash that authentik can decode and records the override in the password-set event.
  • Blueprint password_hash values are stored as supplied without applying these settings.