Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

AD - Connector Remove access LDAP Error attribute conversion operation, data 57, v3839

sreehariv
New Contributor III
New Contributor III

Hello Team,

We are trying to remove one group from the users access through certification campaign revoke option.

Note:  We have integrated Client's one of the ADAM application using AD Connector single domain.

Remove access task got created for that revoked item. After executing the WSRETRY job, it is giving an error  for that task shown below.

2022-09-07 06:01:55,149 [quartzScheduler_Worker-1] ERROR ldap.SaviyntGroovyLdapService  - Exceptionjavax.naming.directory.InvalidAttributeValueException: [LDAP: error code 19 - 00000057: LdapErr: DSID-0C090F95, comment: Error in attribute conversion operation, data 57, v3839�]; remaining name 'CN=XXXXXX,OU=Users,DC=XXXXXX,DC=COM'
    at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3167)

 

we have not configured any update account /remove account or disable account jsons as this is a OOTB feature it seems.

 

can someone from the team confirm is it a known issue from Saviynt side.

we are using v2020.1.2 Saviynt version

I got one reference of the similar issue in this forum where it was mentioned  it was a bug from Saviynt. Link provided below.

https://forums.saviynt.com/t5/general-discussions/ad-connector-issue-with-json/m-p/2092

2 REPLIES 2

rushikeshvartak
All-Star
All-Star

Your attribute value are not unique. Check if below link gives some solution

https://support.oneidentity.com/safeguard-authentication-services/kb/4278005/error-ldap_constraint_v...

If you know this is issue you should create freshdesk ticket to check if patch is available for your version


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

sreehariv
New Contributor III
New Contributor III

Issue Resolved with connector configuration "LDAP OR AD" as changing from LDAP to AD