AuthMe Reloaded

AuthMe Reloaded

3M Downloads

Authy Database migration to AuthMeReloaded Database

Limeen opened this issue · 0 comments

commented

What feature do you want to see added?

Support for migrating Authy data in the /authme converter command. Wiki ↗️

The plugin Authy has not received updates in several years and is no longer actively maintained. As a result, some server owners are considering migrating to AuthMeReloaded, which is more actively supported.

However, a problem arises during the migration process:
Authy stores passwords using SHA-256 without salt, while AuthMeReloaded uses salted hashes. This makes direct conversion impossible without requiring all users to reset or re-enter their passwords.

Are there any alternatives?

I tried to manually move data from the Authy database to the AuthMeReloaded one, but the use of salted hashes in AuthMe made that completely impossible. Since Authy uses unsalted SHA-256 hashes, I couldn’t reproduce compatible hashes for AuthMe without user input.

I also tried using the legacyHashes option in the configuration, hoping AuthMe would recognize the old SHA-256 hashes and rehash them on login:

passwordHash: SHA256

# If a password check fails, AuthMe will also try to check with the following hash methods.
# Use this setting when you change from one hash method to another.
# AuthMe will update the password to the new hash. Example:
# legacyHashes:
# - 'SHA1'

legacyHashes:
- 'SHA256'

Unfortunately, that didn’t work either.

Anything else?

No response