Migration of Users With Passwords

We support migrations of users and their passwords if we can implement the same hash algorithm that is currently used for creation and validation of their passwords. After an old/migrated password is validated the password will be re-hashed to use our modern hashing solution to protect the passwords.

If the hashing alorithm is unknown or is not possible to implement, users can still be migrated and an e-mail can be send to all users with a link where they can create a new password (or use another sign-in alternative). We can also implement more customized migration strategies based on you requirements.

Existing hash algorithm support

We currently have existing support for MembershipHasher (if you are migrating from ASP.NET Membership) and SimpleMembershipHasher (if you are migrating from ASP.NET Simple Membership).

Other migration support

If you have admin UI:s that uses ASP.NET Roles, we have a custom AuthwayRoleProvider that can be used with small modifications on existing code to talk to our admin API:s. Just let us know and we’re happy to share this with you.

The changes needed is likely to handle the fact that Authway is multi-tenant, but Roles (and Membership) have no concept of multi-tenancy. This might force code changes to use are extended methods to pass in the TenantId that should currently be handled or configure a single TenantId that the existing admin UI should work against.