Delimited File Aggregation - Special Characters showing in Entitlements

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Hello - I have recently converted an application that is configured using the delimited file connector from utilizing a .pdf as the file to aggregate to a .csv.

I have successfully got the application to work - however, I noticed that when I go to the “Manage Access” → “Manage User Access” and find the entitlements to request for a user there are special characters present and the entitlements look very funny.

The special characters don’t appear on the entitlements within the entitlement catalog. But they are appearing at the customer facing “Manager User Access” quicklink.

I’m curious if there is a way to remove these special characters so that they don’t appear?

Attached is an example of how they look from the “Manage User Access” quicklink.

image
image780×828 31.3 KB

Here is an example of how the entitlements look within the Entitlement Catalog. There is one entilement in particular that does have some.

image
image750×307 10.5 KB

Also. I did open the .csv in Notepad ++ to see if there are any hidden symbols that appear. It looks like there’s a dot between each word. But that doesn’t explain why there is the weird symbol between each letter.. Notepad++ doesn’t indicate any such symbol or special character between each letter..

image

image

Additionally, I did notice that when I try to select one of the entilements in the “Manage User Access” I get an error like this:

image
image702×113 4.05 KB

Any help will be greatly appreciated!

2

what does it look like within debug?

3

also can you confirm your file is in UTF-8? can run file <filename to check

4

I remember having a similar issue, and the fix was to open the file in Notepad and set the encoding to UTF-8.

image
image546×624 15.7 KB

1 Like
5

When I went to debug, the entitlements looks normal. Without the special characters.

6

When we get the file from the team that downloads the .csv from the application, will we always have to manually go into the file and select UTF-8 in excel?

7

easiest way is definitely to give SailPoint the UTF-8 based file if you can

if that is not an option, can always re-write the contents to a new file in a PreIterateRule

8

I did re-save the file as a UTF-8 based .csv file then attempted to re-aggregate. It looks like the entitlements under the entitlement catalog are still correct, in debug its correct but for whatever reason all the entitlements in the manage user access are still showing the weird characters…

9

I am curious is there a way to manually delete those entitlements in the manage user access? I went to debug and deleted the managedAttributes and went to the entitlement catalog and deleted everything there.. But those entitlements are still showing

10

Hi @MRP4ND4
Can you try to run Full Text Index Refresh task and see if it works. Also, try to examine using Note++ with Hex.

11

I ran the full text index refresh and it removed the bad entitlements. I also ensured that the file was configured properly and the entitlements came through fine now. Thanks for the help everyone!!

12

@Tursun trying to understand this better. Do we need to run “Full Text Index Refresh” after each entitlement aggregation?

13

No, usually don’t need to run Full Text Index Refresh after every entitlement aggregation. SailPoint documentation don’t literally mention special characters, but it says that the Manage Access use an index, and that the index is rebuilt when Full Text Index Refresh runs. So if the index contains bad text or bad encoding/hidden characters during conversion, rebuilding the index is the right way to clear it.
image