This topic has 3 replies, 3 voices, and was last updated 1 month, 3 weeks ago by vliefooghe.
-
AuthorPosts
-
November 30, 2020 at 10:05 pm #28387
ramahadevan
ParticipantThe configuration setup is , IDM is used as Connector to external DS. I am able to create a User via the API, but the user API returns response 404 response .
November 30, 2020 at 11:59 pm #28389Bill Nelson
ParticipantPlease add the request/payload/response to this thread and I will take a look.
You say the user was created in IDM. Please perform a GET on that user and post here as well.
December 1, 2020 at 1:02 am #28390ramahadevan
Participant@Bill Nelson
This is the response , for any operation involving the created users. The user is created in DS
{
“code”: 404,
“reason”: “Not Found”,
“message”: “No Such Entry: The provided entry dc=people,dc=site,dc=ebay,dc=com cannot be added because its suffix is not defined as one of the suffixes within the Directory Server”
}December 2, 2020 at 3:20 pm #28396vliefooghe
ParticipantMaybe there is a mismatch in your provisioner file for LDAP.
From my experience, when IDM makes a create or update, it will then make a GET on the resource to check if the update was OK.
If you have access to your LDAP access logs, you can check what kind of LDAP request is made.
Here it seems to look to “dc=ebay,dc=com” root suffix which is not in your LDAP ?
You have 2 “baseContexts” in the provisioner :
"baseContexts" : [ "dc=myroot,dc=com" ], "baseContextsToSynchronize" : [ "dc=myroot,dc=com" ],
Could you check or show us your baseContexts / baseContextsToSynchronize ?
-
AuthorPosts
You must be logged in to reply to this topic.