user_ldap | 📒 | Identity Management library

The NO_OBJECT error generally means an object with the specified DN (in this case cn=jdoe,ou=managed,ou=domain users,dc=company-corp,dc=global) cannot be found. It's possible to get the error when the service account doesn't have rights to read the record or when the fully qualified DN is incorrect.

To eliminate an incorrect fully qualified DN, you could try searching for an object (like do a search for sAMAccountName=LogonIDGoesHere) and retrieving the DN value.

To eliminate access, you can check an account's effective permissions to an object using Active Directory Users & Computers. On the "Security" tab, click "Advanced". In the advanced security settings window, click on the "Effective Access" tab. Click the 'select a user' link to select your service account then click "View effective access" to see if something like 'read all properties' or 'read general information' are allowed.

Add the customs attributes in "Active Directory Schema" and assign to user class as optional attribute, after runed my code and successful result