Business descriptions are applied incorrectly when using a wildcard with an underscore in RSA Identity Governance and Lifecycle
4 years ago
Originally Published: 2016-10-14
Article Number
000042791
Applies To
RSA Product Set: Identity Management and Governance
RSA Version/Condition: Prior to 6.9.1 P18, 7.0.0 P05, 7.0.1 P01
 
Issue
When applying business descriptions using wildcard (%) with an underscore (_) the description gets applied incorrectly because it is evaluating the underscore as a single character wildcard instead of matching on an underscore. Underscore should not be considered a wildcard.

The example below is input from a CSV file. We'll focus on the %_User filter on the third line below:
ApplicationRole,Perforce,FALSE,%_Admin,,"short desc for any admin perforce role","long desc for any admin perforce role"
ApplicationRole,Perforce,FALSE,%_Approver,,"short desc for any approvers perforce role","long desc for any approvers perforce role"
ApplicationRole,Perforce,FALSE,%_User,,"short desc for any users perforce role","long desc for any users perforce role"

When importing the above file:
Importing new business descriptions from the above CSV file.

Notice the filter %_User applied the descriptions to an application role with User in the name but no underscore.  "Depot User" had the the descriptions applied incorrectly. They were applied correctly for Master_Num1_User.
Notice the filter %_User applied the descriptions to an application role with User in the name but no underscore.
Resolution
This issue has been fixed in RSA Identity Governance & Lifecycle 6.9.1 P18, 7.0.0 P05, 7.0.1 P01 and beyond.

If you are using an XML import for your business descriptions, instead of through the UI or a CSV file, you will need to replace the _  in the filter with #_ for it to match properly. The underscore needs to be escaped with a #. This work around will only work in the fixed versions of RSA Identity Governance & Lifecycle.