000036121 - Identities with replacement characters showing block instead of characters in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Apr 17, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036121
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.0.0
 
Issue
User data collected from a .csv file with words having replacement characters, such as ê, display incorrectly in our user interface.
 


User-added image
CauseWhen the HXTT driver reads the .csv-file, it uses client's default character set (which is set through Linux environment variables), unless the charSet property is set explicitly to use a particular set. However, Unicode files need to have ByteOrderMark to describe itself to the reader. Most likely, even if the JVM runs in UTF-8 locale, the absence of the ByteOrderMark in the file might make the reader to fall back to ASCII set.

Essentially, whenever a non-ASCII file needs to read by HXTT driver, the charSet parameter always needs to be supplied in the URL to ensure the proper character set is used for the data.
ResolutionModify the collector configuration by adding the charSet=ISO-8859-1 in the connection URL.  For example:

jdbc:csv:///////home/oracle/database/SampleData/AveksaData?_CSV_Header=true;charSet=ISO-8859-1;_CSV_Quoter=";

 



 

Attachments

    Outcomes