Provisioning IN LDAP - Getting LDAP error code 65

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi All,

I am able to do provision for LDAP with default attributes in Sailpoint IdentityNow (whatever attributes are there in the create account section when we setup a fresh LDAP connection). The account is created in LDAP, but when I try to add one extra attribute in the create account section in sailpoint identityNow, it is giving me LDAP error code 65.

NOTE: All these attributes I have also added to the account schema.

Can anyone give any suggestions on how to proceed further? If you have any questions about the problem, I can elaborate more on that.

Thank you in advance.

2

Can you share what attribute you are adding and may be your plan or request?

3

I have a few extra attributes other than the default attributes, which are listed in the create section. Example: employeeid is an attribute in LDAP, but it was not populated in the create section for the account. So when I try to add an employeeid in the Create section and do provisioning, it is giving LDAP error code 65. It is the same with all other attributes.

4

Hi @Pucha_Rohan_12 , LDAP: error code 65 is Object Class Violation.
It looks like the extra attribute added to your account schema belongs to a different object class which you are not passing in the Create Profile of your source.
Can you check the object class of that attribute and try add it on the object class property in your Create Profile policy?

HTH

5

Can you please guide me on how to add multiple object class values to the Create Provisioning Policy?

6

Hi Rohan,

you can add as below

import java.util.List; import java.util.ArrayList; 
          list = new ArrayList();

          list.add("bbyperson");
          list.add("inetOrgPerson");
          list.add("organizationalPerson");
          list.add("person");
          list.add("top");
          list.add("shadowAccount");
          list.add("posixAccount");

          return list;
        </Source>
      </Script>
    </Field>
7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.