CHECKFORUNIQUE not working for AD Connector

[ShubhamBabbar]

Upon checking for UPN uniqueness in AD connector using the below logic:

{"userPrincipalName": "${if(type.equals('Service Account')) {prefix+'-'+term+'-Svc'+task.endpoint?.customproperty1} else {prefix+'-RES0001'+task.endpoint?.customproperty1}}###${if(type.equals('Service Account')) {prefix+'-'+term+'-Svc'+task.endpoint?.customproperty1} else {prefix+'-RES0002'+task.endpoint?.customproperty1}}"}

I am getting the below error:

Error while searching for userPrincipalName=A2-RES0001@domain.com-[LDAP: error code 32 - 0000208D: NameErr: DSID-03100221, problem 2001 (NO_OBJECT), data 0, best match of:

2024-07-30T23:40:28+05:30-ecm-worker-ldap.SaviyntGroovyLdapService-quartzScheduler_Worker-15-ggr94-ERROR-Error while creating account in AD - [LDAP: error code 68 - 00000524: UpdErr: DSID-031A11FA, problem 6005 (ENTRY_EXISTS), data 0

Ideally in this scenario UPN should be created as A2-RES0002@domain.com after checking for A2-RES0001@domain.com

The createaccountjson does not have contain mapping for UPN.

[rushikeshvartak]

{
"userPrincipalName": "${if(type.equals('Service Account')) {prefix+'-'+term+'-Svc'+task.endpoint?.customproperty1} else {prefix+'-RES0001'+task.endpoint?.customproperty1}}###${if(type.equals('Service Account')) {prefix+'-'+term+'-Svc'+task.endpoint?.customproperty1} else {prefix+'-RES0002'+task.endpoint?.customproperty1}}"
}

[ShubhamBabbar]

@rushikeshvartakThanks for you response, I have used the same logic as mentioned in my question as well. I don't see any difference in your JSON and the mine which is not working for me. 

[rushikeshvartak]

Could you kindly provide a detailed snapshot of the information extracted from the logs, encompassing errors and other pertinent functionality details encountered during the execution of this process? Your assistance in furnishing this information would greatly aid in the analysis and resolution of any issues .



‼️‼️⚠️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.⚠️‼️‼️

[ShubhamBabbar]

@rushikeshvartak logs are attached in the my initial query as well, pasting it here again:

Error while searching for userPrincipalName=A2-RES0001@domain.com-[LDAP: error code 32 - 0000208D: NameErr: DSID-03100221, problem 2001 (NO_OBJECT), data 0, best match of:

2024-07-30T23:40:28+05:30-ecm-worker-ldap.SaviyntGroovyLdapService-quartzScheduler_Worker-15-ggr94-ERROR-Error while creating account in AD - [LDAP: error code 68 - 00000524: UpdErr: DSID-031A11FA, problem 6005 (ENTRY_EXISTS), data 0

[rushikeshvartak]

Looking for logs in text file with to check all details

[NM]

Hi @ShubhamBabbar , can you share your account name rule?

[ShubhamBabbar]

@NM 
AccountNameRule: CN=${if(type.equals('Service Account')) {prefix + '-' + term.replaceAll(',','') + '-Service,' + task.endpoint?.customproperty2} else {prefix+' '+resourceType+' '+termResource.replaceAll(',','')+','+ task.endpoint?.customproperty3 }}

@rushikeshvartak PFA logs

[rushikeshvartak]

Does user already exists ?

"2024-07-31T07:06:47.004+00:00","ecm-worker","ldap.SaviyntGroovyLdapService","quartzScheduler_Worker-17-ggr94","ERROR","Error while creating account in AD - [LDAP: error code 68 - 00000524: UpdErr: DSID-031A11FA, problem 6005 (ENTRY_EXISTS), data 0"

[ShubhamBabbar]

@rushikeshvartak  Yes A2-RES0001@domain.com UPN exists in a different OU in the same directory thats why check for unique should use the second option A2-RES0002@domain.com

[NM]

Hi @ShubhamBabbar , in short you are trying to create an account in an different OU and once you did a check based on UPN it was able to find an account in different OU but didn't use incremental rule defined in checkforunique right?

[ShubhamBabbar]

That is correct @NM 

[rushikeshvartak]

What is your base DN ?