¶ Migrate users to Authing

If you have users from the original user system that need to be imported into Authing, please be sure to read the guidelines in this section.

If you want to smoothly migrate users to Authing, you need to use custom database functions and write corresponding database scripts. When the user authenticates for the first time, the user will be authenticated with the custom data script you configured. After the authentication is successful, it will be migrated to the Authing database. When the user authenticates for the second time, the Authing database will be used for verification. When all users are authenticated at least once, the migration process is complete. For details, please refer to Lasy migration of users to Authing。

If you want to store user data in your own database and don't want to expose user data to Authing, you can use a custom database to save user data.

You can also choose to import all users into Authing at one time. We provide API & SDK to help you quickly write import scripts. For details, please refer to Importing users using SDK. In this process, you also need to confirm a question first: Can you get the user's plaintext password? If you can get it, just use the plaintext password to create a new user. If not, you need to write a customer password function first, So that when the user logins in to Authing, the custom password you write will be used for encryption and verification Function. The user’s previous password can still take effect without requiring the user to reset his password.

If you belong to the usage scenario of internal employees（EIAM）, you can also download from LDAP Server (opens new window), Windows local Active Directory (opens new window), etc. The third-party corporate identity source is imported into the organization and user directory. For details, please refer to here.