AD LDAP User Import Fail

[ShubhamBabbar]

On trying to import users from AD LDS using OOTB AD Connector, we are seeing the following error:
Incorrect string value: '\xF0\xA3\x98\xBA \xE4...' for column 'CUSTOMPROPERTY7' at row 1

User_Attribute mapping for CUSTOMPROPERTY7 :  CUSTOMPROPERTY7::displayName#String

Solution tried but failed:  CUSTOMPROPERTY7::displayName#emchar

We are also unable to identify the user causing this issue in AD because of the incomplete logs not mentioning any other user details.

 

[rushikeshvartak]

• Its due to special characters /emoji in display name 
• identify such characters and remove from displayname

[ShubhamBabbar]

Hi Rushikesh,

Thanks for responding. I recognize this is because of special characters, but logs give no information about which is the user. Can you please let me know if it is possible:

• Is it possible to identify the user having emoji in Saviynt or AD through an LDAP filter?
• Can we import the users with such characters in Saviynt?

[rushikeshvartak]

• Is it possible to identify the user having emoji in Saviynt or AD through an LDAP filter? - No
• Can we import the users with such characters in Saviynt? - No

You need to ask for extract from AD Team and identify special characters 

[ShubhamBabbar]

We identified it to be a Japanese character and not an emoji, as per this article MySQL's utf8 is assumed to be 3 bytes, so it cannot handle 4-byte UTF-8.

[rushikeshvartak]

Yes please remove character and run import

[ShubhamBabbar]

We cannot remove the character, its a part of the name coming from auth source data. We have to import it.

[rushikeshvartak]

If its third party character you can't import.

We have also faced similar issue. You can raise idea ticket similar like below

https://ideas.saviynt.com/ideas/EIC-I-5080 

[Manu269]

refer post here for similar case :

Solved: Comma in Distinguished Name not getting processed ... - Saviynt Forums - 32762

[ShubhamBabbar]

Hi Manu,
The post you have mentioned refers to a different use case.