Click HERE to see how Saviynt Intelligence is transforming the industry. |
07/03/2024 02:32 AM
Dear Team,
We need assistance for Saviynt to accept special character in user's name(CN, display name, first name or last name). Currently Saviynt is having issue to complete update AD account task, and the error is pointing to special character in the name.
There is a user with the user name like --xx D/o xx. When any attribute of the user is updated and simultaneously the task triggers basis the rule, the task gets stuck in pending state and it gives the error message " Error while update operation for account, LDPA error code=1
When Saviynt triggers the task due to the special character in the name of the user the tasks are stuck in pending state.
We have updated the "updateaccountjson" as -${cn?.replace('/', '\\\\,')?.replace('/','\\/')} in the lower environment to test.
However, post the rule trigger the update account task throws the below error:
Error: Error while Update operation for account-sglfiam9 in AD - [LDAP: error code 1 - 000020D6: SvcErr: DSID-031007FA, problem 5012 (DIR_ERROR), data 0 ]
We have a requirement to manage the below special characters in the user's name:
The special characters are: - / , ' . @ ()
Requesting you to assist in providing inputs on the same.
Regards,
Manpreet Kaur
07/03/2024 02:54 AM - edited 07/03/2024 02:57 AM
@Manpreet_Kaur try below
${cn?.replace(',', '\\\\,')?.replace('/','\\/')}
07/03/2024 09:27 PM
"cn": "${cn?.replace(',', '\\2C')?.replace('=', '\\3D')?.replace('+', '\\2B')?.replace('<', '\\3C')?.replace('>', '\\3E')?.replace(';', '\\3B')?.replace('\\', '\\5C')?.replace('\"', '\\22')?.replace('#', '\\23')?.replace('\'', '\\27')?.replace('/', '\\2F')}",
07/07/2024 07:17 PM
Hi @rushikeshvartak / @Raghu
Thanks for your inputs.
We are currently testing with the given options and will get back.
Regards,
Manpreet Kaur
07/24/2024 07:26 PM
Hi @Manpreet_Kaur ,
Are you able to resolve this error during UpdateAccount task for AD Account with special char forward slash "d/o" or "s/o" ?
We also getting same LDAP error as your scenario.
Regards,
Wei Xiang