We are encountering an issue where attempting to update a user’s details via the Management API is affecting the wrong user record. Our users may have the same username, email, and user_id but are differentiated by connections (ESP-IAT vs. ESP-UAT). When we specify to update the user from the ESP-IAT connection, the changes are incorrectly applied to the user in the ESP-UAT connection.
Attached are the logs from our recent attempt. The request specifies the ESP-IAT connection, but the response reflects changes to the ESP-UAT user. We need to ensure that API calls target and update the correct user record based on specified connection identifiers.
Could you please assist us in resolving this issue?
{
“date”: “2024-05-08T14:01:36.436Z”,
“type”: “sapi”,
“description”: “Update a User”,
“client_id”: “dummyclientid”,
“client_name”: “”,
“ip”: “128.127.114.245”,
“details”: {
“request”: {
“method”: “patch”,
“path”: “/api/v2/users/auth0%7Crazvan.mestereaga+ait03identifier1@globallogic.com”,
“query”: {},
“body”: {
“connection”: “ESP-IAT”,
“email”: “razvan.mestereaga+ait03identifier1@globallogic.com”,
“given_name”: “Alin”,
“name”: “Alin BCA IT OKTA Confirmed2”,
“family_name”: “BCA IT OKTA Confirmed2”
},
“channel”: “api”,
“auth”: {
“user”: {},
“strategy”: “jwt”,
…
“response”: {
“statusCode”: 200,
“body”: {
“created_at”: “2024-04-29T09:52:18.975Z”,
“email”: “razvan.mestereaga+ait03identifier1@globallogic.com”,
“email_verified”: false,
“family_name”: “BCA IT OKTA Confirmed2”,
“given_name”: “Alin”,
“identities”: [
{
“connection”: “ESP-UAT”,
“user_id”: “razvan.mestereaga+ait03identifier1@globallogic.com”,
“provider”: “auth0”,
“isSocial”: false
}
],
“name”: “Alin BCA IT OKTA Confirmed2”,
“nickname”: “razvan.mestereaga+ait03identifier1”,
“picture”: “dummy.png”,
“updated_at”: “2024-05-08T14:01:36.430Z”,
“user_id”: “auth0|razvan.mestereaga+ait03identifier1@globallogic.com”,
“user_metadata”: {
“preferred_language”: “en-GB”
}
}
}
},
“auth0_client”: {
“name”: “Auth0.Net”,
“version”: “7.26.0”,
“env”: {
“target”: “NET462”
}
},
“$event_schema”: {
“version”: “1.0.0”
},
}