So the update for this doc snippet updating two things:
1.) Decoding the user password hash
- currently we don't so when a dev performs import the password hash is getting double encoding leading to invalid password errors when the correct password is provided for a newly imported user
2.) Updating the decoding functions so the hash.Scrypt key uses standard base64 encoding and user password hashes uses base64URL encoding
- currently the snippet doesn't decode the use password hash, but it should using a base64URL encoding

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.