Issue:
Exception Occurred while provisioning user on active directory from OIM(Oracle Identity Manager):
Error while creating user [[org.identityconnectors.framework.common.exceptions.ConnectorException: There is no such object on the server.^M
Investigation & Cause:
Check oim_server1-digaonistic.log and connector server logs for more details and to find the cause of provisioning failure.
This indicates that the specific object could not be found in directory. This issue may occur when:
1. The Manager Name value is incorrect i.e the DN of the user's manager is incorrect.So when a provisioning requests goes to AD,it tries to set the user's manager with populated value during provisioning ,so the manager should be already present and should match.If incorrect manager DN is set ,then AD doesn't find a match and returns a "no such object on server exception".
2. The OU where you're trying to provision user isn't exist.
Solution:
1. Check the manager name is correctly populated. Manager Name is not a mandatory attribute, but if populated, it should be in proper DN format.(AD expects manager’s DN name)
e.g: DN: cn=abc,ou=lmn,dc=corp,dc=com in AD,where abc is user's manager.
2. Make sure that the organizational unit that you want to use exists in the Active Directory.
Exception Occurred while provisioning user on active directory from OIM(Oracle Identity Manager):
Error while creating user [[org.identityconnectors.framework.common.exceptions.ConnectorException: There is no such object on the server.^M
Investigation & Cause:
Check oim_server1-digaonistic.log and connector server logs for more details and to find the cause of provisioning failure.
This indicates that the specific object could not be found in directory. This issue may occur when:
1. The Manager Name value is incorrect i.e the DN of the user's manager is incorrect.So when a provisioning requests goes to AD,it tries to set the user's manager with populated value during provisioning ,so the manager should be already present and should match.If incorrect manager DN is set ,then AD doesn't find a match and returns a "no such object on server exception".
2. The OU where you're trying to provision user isn't exist.
Solution:
1. Check the manager name is correctly populated. Manager Name is not a mandatory attribute, but if populated, it should be in proper DN format.(AD expects manager’s DN name)
e.g: DN: cn=abc,ou=lmn,dc=corp,dc=com in AD,where abc is user's manager.
2. Make sure that the organizational unit that you want to use exists in the Active Directory.
No comments:
Post a Comment