search cancel

CA PAM CSV Reports show locale-specific characters incorrectly encoded


Article ID: 199447


Updated On:


CA Privileged Access Manager - Cloakware Password Authority (PA)


When generating a CSV report for password view or any other credential-management operation, if the text displayed contains non-standard ASCII characters (for instance those specifically associated to the Spanish locale, like é or ü) those specific non-standard ascii characters are not correctly encoded and show up as garbled (for instance Ó shows up as ”)




CSV files can be created in many text editors or spreadsheet programs and saved as plain text.

The report csv file is UTF-8 encoded, so all non-English characters are encoded in UTF-8. The tools that one uses to browse the results need to be aware of this encoding. If those tools are not configured to recognize UTF-8 encoded characters, the result will be garbled, explained in the introduction.



As mentioned before, the application we are using to see the csv report needs to be aware of the UTF-8 encoding. Here are few examples:

1. If you use notepad++ the tool will automatically recognize UTF-8 encoding and show Spanish characters correctly.

2. If you use Microsoft Notepad you need to tell the editor about UTF-8 encoding and then the characters will be handled correctly.

In any case if special characters such as UTF-8, Cyrillic or Chinese require displaying, confirm that your application supports them. Your version of Microsoft Excel® or Google Drive, for example, may or may not have that support.

Here is an example: In the screenshot below, a CSV file has been opened with notepad indicating UTF-8 encoding must be used. You can see that comments for user "valdo" contain correct Spanish characters.

Here is another example opening the CSV file using excel and configuring it to pick up UTF-8 encoding

We can see that by choosing the right separator and specifying the File origin as UTF-8 encoding, the right data is displayed

Additional Information