Getting error during AD creation

Hi Team,

I’m getting error during Creation of AD below is the error .

Please find below error for ref.

Error generating a unique value, the exception was: java.lang.Exception: Unable to contact connector to generate unique value and is not retry-able. Action:UniqueAccountIdValidator: Calling getObject for objectType ‘account’ using id ‘CN=testfn102, testln10249 (sbs999952),ou=users,ou=TCS,ou=hospitals,ou=sb-departments,dc=XXX,dc=’ and options ‘{cloudConfigOverrides={aggregateTimeout=30, disablePooling=true, timeout=30}}’ on source ‘ActiveDirectorySecondarySource [source]’. Exception: sailpoint.connector.ConnectorException: Failed to find connection settings for the dc=xxx,dc=

Thank you,
Saikumar

From Account activity in Search, verify the correct FQDN is being setup in the provisioning plan

the last dc= is missing value in 'CN=testfn102, testln10249 (sbs999952),ou=users,ou=TCS,ou=hospitals,ou=sb-departments,dc=XXX,dc=’

Please provide the correct distinguishedName in the Source Account Create Profile page and retry creation.

Hi @shravari,

Thank you for reply .

Yes seems like this is DN length issue ,Can you le me know how to resolve this issue.

Thank you,
Saikumar

maximum length of dn is 255 characters which doesn’t seem the case here. Have you masked the values dc=XXX,dc= ? If not then your code/config/transform has issue.

Hi Aditya,

We are able to provision 35 char length OU but below 60+char OU’s not able to provision

CCC/CKH/BHS-35
TCS-64
CTS-66
KSC-67

refer this Active Directory Maximum Limits Scalability Capacity | Microsoft Learn

you might need to talk to your ad team to understand the feasibility of increasing the length , else you need to tweak you create profile / provisioning policy to provision values within permitted length

1 Like

Check with your AD Team

1 Like

In your AD Create Profile source code, verify that you have not specified any soft limit for distinguishedName attribute like

"cloudMaxSize": "100" 

If yes, please modify it to meet your requirements.

2 Likes

Thank you Sharvari …We are able to provision now after changing cloudMaxSize to 200 :slight_smile:

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