and more in a single search tool across platforms. Read the announcement here. |
04/20/2023 03:41 AM
Hi,
I have configured the AD connector with few attributes for account creation and at the time of provisioning it is throwing a "Name Error". Please find the attachment. Also attaching the account name rule and create account json
CN=${user.firstname},OU=Users,OU=Location C,OU=GPO Testing, OU=IT,DC=XXX,DC=NET
04/20/2023 04:53 AM
It seems ou does not exist
04/20/2023 09:18 AM
I have copied the OU from AD itself
04/20/2023 06:42 AM
Hello @archita_95,
If you are getting LDAP error code 32, it means that the server cannot find the object you are trying to access.
This error often comes with a message like "no such object" or "invalid DN syntax". However, it can also occur if the service account you are using to connect to the AD does not have sufficient privileges to access the object.
To resolve this issue, you should check the OU location and make sure that it is correct. You can then update the account name rule to reflect the correct location. Additionally, you should ensure that the service account you are using has the necessary permissions to access the object.
Thanks,
04/21/2023 02:05 AM
Hello @archita_95,
Please ensure that the user account being created has a linked manager and that the manager's DN is valid. The account should be created in the correct DN and should be in active status.
Thanks,
04/24/2023 03:20 AM
Hi, I have tried account creation with active manager and valid manager's DN (which is active) but same error I am getting
04/24/2023 03:39 AM
Hello @archita_95 ,
can you please share what you are seeing in the log?
Thanks,
04/24/2023 05:35 AM