Description:
During a bulk user import into Auth0, I noticed that the identities.connection
field in the imported user data retains the database connection name of the original database from which the data was exported. This is happening despite the users being imported into a new database connection within the same tenant.
Additionally, users in the new database connection have the same user_id
values as the users in the old database connection.
For example:
- Original database connection:
old-database-connection
- New target database connection:
new-database-connection
- After import, the
identities.connection
field for each user still showsold-database-connection
.
User in new database connection
"identities": [
{
"connection": "old-database-connection",
"user_id": "",
"provider": "auth0",
"isSocial": false
}
],
Questions:
- Why isn’t the
identities.connection
field updated to reflect the name of the new database connection during the import process? - Will this discrepancy cause any issues? Specifically:
- Management: Will it interfere with managing these users under the new database connection?
Additional Context:
- The original database connection still exists in the same tenant.
- The import job completes successfully without errors.
- All other fields in the imported user profiles seem accurate.
I would appreciate clarification on whether this behavior is expected and any potential consequences of leaving the identities.connection
field unchanged. If this could lead to issues, what would be the recommended steps to correct it?
Thank you!