2 ms·
If the provider is worth its salt¹ it will prefix the stored password with the hash that was used. That way it can update the hash when the user next logs in if
by anotherevan 5mo ago
If the provider is worth its salt¹ it will prefix the stored password with the hash that was used. That way it can update the hash when the user next logs in if it is out of date.
E.g.: {argon2}…
¹ See what I did there?
- nkmnz 5mo agoI see what you did there, but I assume you mean "prefix the stored hash with the algorithm that was used", right? I still don't know how this would help with a migration, though. They would still need to run both auth systems in parallel until every single user has logged in again - or force everyone to create a new password. Right?
- anotherevan 5mo agoAssuming you get get access to the hashed passwords the other party used as part of the migration data, and you know what hash was used for them, then there's nothing to stop you using them yourself. But in reality, I doubt they would release either of those things.