Import users in bulk from Auth0

This topic is for people who want to import users in bulk to Kinde from Auth0. For other formats, see import users via JSON or CSV.

File requirements

Link to this section

• Auth0 data - User details and passwords need to be in NDJSON (Newline Delimited JSON) format
• File size up to 20MB supported

If you’ve got large user sets (over 20MB) or are concerned about file size limits, you might consider importing in batches, or contact us for import support.

Before you import users

Link to this section

• Create organizations in Kinde - only if you use this function to support multi-tenancy (for example, in a B2B structure) or if you manage separate user groups this way.
• Add roles and permissions in Kinde, if you intend to import these details with users.
• If your users sign on with passwords, make sure you Enable password authentication before importing them

Cases in usernames

Link to this section

Kinde treats usernames as case-insensitive. In other words, we ignore case. We do this because it eliminates the possibility of auth issues and fraud when two usernames are identical in every aspect except the case of one of their letters.

We are happy to support users choosing an aesthetically pleasing username combination, like RosyRose or BuilderBob. We just don’t also support separate identities for rosYrosE and BUilderbob. Before importing users, we recommend checking that all usernames are unique in more than just case.

Prepare Auth0 data

Link to this section

When you export user details from Auth0:

• select all the default fields and add the identities field to the import list.
• select the JSON file format for export.

Identities data distinguishes the type of identity, specifically the connection attribute. e.g. username, phone, GitHub, Google, etc.

How Auth0 user identities are treated on import

Link to this section

Social identities without an email can be imported, and are identified by the connection type. You can import users with multiple identities, these will be listed under the user’s profile.

Kinde supports migrating the following authentication methods from Auth0: Usernames, Email, Phone, Google, Apple, Microsoft, Facebook, GitHub, Twitch, Bitbucket. Auth methods are shown in the connection attribute. These are represented as follows in the identity data:

• Username-Password-Authentication
• email
• sms
• google-oauth2
• apple
• microsoft
• github
• twitch
• facebook
• bitbucket
• windowslive

Import options

Link to this section

When importing users from Auth0, you have two options:

1. Import users only - choose this method if you want to allow users to reset their password or sign in another way.
2. Import passwords only - only choose this if you have already imported users.

How to import users

Link to this section

1. In Kinde, go to Users, then select Import users.
2. Select From Auth0.
3. Follow the on-screen prompts to import the data.
4. If there are any errors with the import, you will be able to view them afterwards.
5. Most import errors can be fixed by editing the JSON file and then re-importing into Kinde. Any records that have already been imported and are unchanged, will be ignored.

Impact on end-users

Link to this section

Importing all your existing users and passwords should mean that your end users won’t notice anything when they next sign in. This is the optimal experience. However:

• If a user changes their password after the user export and while the migration is in progress, they will be prompted to reset their password on the next sign in.
• If you have set up a new authentication method as part of the user migration (for instance, going passwordless) your users will be prompted to use the new method on sign in.
• If you add or remove roles or permissions, they may gain/lose access to parts of your system.

Weak passwords are not rejected on import

Link to this section

When you import passwords, Kinde does not check for password strength. However, if you do not also include a TRUE in the password_verified column of the CSV, Kinde will send a one-time password to the user the first time they try to sign in, in order to verify their identity.

In future, we may add the ability to check password strength and initiate a password change if it’s deemed to weak by standard password criteria.

Re-importing can update user info

Link to this section

If you add a user via import and they start authenticating via Kinde, and then you import their records again with changes - for example, you import name and email, but with a new permission - that information will be updated Kinde. We do not recommend making user updates via import, instead, manage updates via the Kinde admin, or via API.

Communication to users

Link to this section

Kinde does not send any notifications or invitations to users when they are added to Kinde via import. The idea is that your users have a seamless experience that feels (almost) like it always has in your app.

If you’ve made changes to their sign in experience — for example adding multi-factor authentication — then consider contacting your users to let them know their sign in experience will be changed.