Password hash migration transfers a customer's hashed password from a legacy system to a new one, so the customer can keep signing in with their existing password instead of resetting it.
Frequently asked questions
What password hash formats are supported for migration?
Strivacity supports importing several hash algorithms, including Argon2, BCrypt, and SHA256Salted (its own default format), among others, so credentials from a range of legacy systems can be preserved during import.
What happens to the password hash after the customer's first sign in?
It's automatically re-hashed using the new system's default algorithm, without the customer noticing.
Was this definition useful?
Feedback goes to the editor who maintains this entry.
.avif)