Password hashing algorithms need upgrading over time, but hashing is one-way so you can't simply convert existing hashes. The solution is a zero-downtime migration pattern: register both old (PBKDF2) and new (Argon2) hashers using .NET keyed services, attempt verification with the new algorithm first, fall back to legacy on

6m read time From milanjovanovic.tech
Post cover image
Table of contents
The Naive Approach and Why It FailsThe Solution: Migration on LoginImplementation with .NET Keyed ServicesReal-World ImprovementsFinishing the MigrationSummary

Sort: