How to Migrate a Password Hash
Edit this pageHow to Migrate a Password Hash
4.4
Password migration was introduced in Symfony 4.4.
In order to protect passwords, it is recommended to store them using the latest
hash algorithms. This means that if a better hash algorithm is supported on your
system, the user's password should be rehashed using the newer algorithm and
stored. That's possible with the migrate_from option:
- Configure a new Encoder Using "migrate_from"
- Upgrade the Password
- Optionally, Trigger Password Migration From a Custom Encoder
Configure a new Encoder Using "migrate_from"
When a better hashing algorithm becomes available, you should keep the existing
encoder(s), rename it, and then define the new one. Set the migrate_from option
on the new encoder to point to the old, legacy encoder(s):
- YAML
- XML
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
# config/packages/security.yaml
security:
# ...
encoders:
# an encoder used in the past for some users
legacy:
algorithm: sha256
encode_as_base64: false
iterations: 1
App\Entity\User:
# the new encoder, along with its options
algorithm: sodium
migrate_from:
- bcrypt # uses the "bcrypt" encoder with the default options
- legacy # uses the "legacy" encoder configured aboveWith this setup:
- New users will be encoded with the new algorithm;
- Whenever a user logs in whose password is still stored using the old algorithm, Symfony will verify the password with the old algorithm and then rehash and update the password using the new algorithm.
Tip
The auto, native, bcrypt and argon encoders automatically enable
password migration using the following list of migrate_from algorithms:
- PBKDF2 (which uses hash_pbkdf2);
- Message digest (which uses hash)
Both use the hash_algorithm setting as the algorithm. It is recommended to
use migrate_from instead of hash_algorithm, unless the auto
encoder is used.
Upgrade the Password
Upon successful login, the Security system checks whether a better algorithm is available to hash the user's password. If it is, it'll hash the correct password using the new hash. If you use a Guard authenticator, you first need to provide the original password to the Security system.
You can enable the upgrade behavior by implementing how this newly hashed password should be stored:
After this, you're done and passwords are always hashed as securely as possible!
Provide the Password when using Guard
When you're using a custom guard authenticator,
you need to implement PasswordAuthenticatedInterface.
This interface defines a getPassword() method that returns the password
for this login request. This password is used in the migration process:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
// src/Security/CustomAuthenticator.php
namespace App\Security;
use Symfony\Component\Security\Guard\PasswordAuthenticatedInterface;
// ...
class CustomAuthenticator extends AbstractGuardAuthenticator implements PasswordAuthenticatedInterface
{
// ...
public function getPassword($credentials): ?string
{
return $credentials['password'];
}
}Upgrade the Password when using Doctrine
When using the entity user provider, implement
PasswordUpgraderInterface in
the UserRepository (see the Doctrine docs for information on how to
create this class if it's not already created). This interface implements
storing the newly created password hash:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
// src/Repository/UserRepository.php
namespace App\Repository;
// ...
use Symfony\Component\Security\Core\User\PasswordUpgraderInterface;
class UserRepository extends EntityRepository implements PasswordUpgraderInterface
{
// ...
public function upgradePassword(UserInterface $user, string $newEncodedPassword): void
{
// set the new encoded password on the User object
$user->setPassword($newEncodedPassword);
// execute the queries on the database
$this->getEntityManager()->flush();
}
}Upgrade the Password when using a Custom User Provider
If you're using a custom user provider, implement the PasswordUpgraderInterface in the user provider:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
// src/Security/UserProvider.php
namespace App\Security;
// ...
use Symfony\Component\Security\Core\User\PasswordUpgraderInterface;
class UserProvider implements UserProviderInterface, PasswordUpgraderInterface
{
// ...
public function upgradePassword(UserInterface $user, string $newEncodedPassword): void
{
// set the new encoded password on the User object
$user->setPassword($newEncodedPassword);
// ... store the new password
}
}Trigger Password Migration From a Custom Encoder
If you're using a custom password encoder, you can trigger the password
migration by returning true in the needsRehash() method:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
// src/Security/CustomPasswordEncoder.php
namespace App\Security;
// ...
use Symfony\Component\Security\Core\Encoder\PasswordEncoderInterface;
class CustomPasswordEncoder implements PasswordEncoderInterface
{
// ...
public function needsRehash(string $encoded): bool
{
// check whether the current password is hash using an outdated encoder
$hashIsOutdated = ...;
return $hashIsOutdated;
}
}
