Facing issues while provisioning

Hey guys,

While provisioning into target ADLDS(using ADAM CONNECTOR) i can provision the accounts by help of the default attributes (attributes provided in create account section) but when i tried to add the custom attributes as per the requirement and tried to rpovision i am getting an error. i am attaching screenshto of it. pls help me how can i provision with all the custom attributres . thanks

Hi @Apoorv0802,

Can you share the provisioning policy for your custom attributes? Is adding any custom attribute to the policy causing the error or just one custom attribute that is problematic?

Hey Varshini,

I am able to crate the account with the default attr (sn,dn,givenname) but whenevr i enable any custom attribute the account dont get created and i get error (Provisioning
sailpoint.connector.ConnectorException: [LDAP: error code 65 - 0000207D: UpdErr: DSID-03151D3B, problem 6002 (OBJ_CLASS_VIOLATION), data -1770594129 ],sailpoint.connector.ConnectorException: [LDAP: error code 65 - 0000207D: UpdErr: DSID-03151D3B, problem 6002 (OBJ_CLASS_VIOLATION), data -1770594129 ]
SHOW LESS) whwen i tried provisoing woth custom atribute.

You might need to check which certain custom attributes are allowed for each object class (like userProxyFull, top, person…) What are the values of objectClass attribute that you have indicated in your create account policy?

Thanks!

1 Like

Try only allowing one extra attribute at a time, beside the defaults, to help identify which attribute(s) is causing the problem. Once identified it may be a matter of reviewing the schema for the attribute.

Hey SO THIS IS MY objectClass

top

person

organizationalPerson

user


is it correct way of putting objectclass?? because this is the object class i found from the target system
image

I assume that the objectClass in your policy looks something like this:

{
  "attributes": {
    "cloudDelimiter": ";"
  },
  "isRequired": false,
  "isMultiValued": true,
  "name": "objectClass",
  "transform": {
    "attributes": {
      "value": "top;biibRequests;biibResources;person;biibPerson"
    },
    "type": "static"
  },
  "type": "string"
}

Like @ts_fpatterson said, troubleshoot by adding custom attribute one by one to the policy with different combinations of objectclass to find which attribute(s) are allowed and not allowed for each object class in your target system.

Thanks!

it is like this

“attributes”: {
“value”: “{"top", "person", "biibPerson", "biibResources", "biibRequests"}”

in create account i defined it like this

can u pls rply on query