The display sequence of custom User Attribute Separators is incorrectly and unpredictably modified after making edits to User Attributes in RSA Identity Governance & Lifecycle
3 years ago
Originally Published: 2020-01-08
Article Number
000042419
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.0.x, 7.1.x
 
Issue
In RSA Identity Governance & Lifecycle, the Admin > Attributes > User tab is used to edit/create user attributes. Separators may be used to categorize these attributes and sort them into a particular order or sequence for display on the Admin > Attributes > Users tab and on the Users > Users > {user name} > General tab. However, the defined order of these attributes for display on these pages is incorrectly and unpredictably modified when any edits are made to the Admin > Attributes > Users tab.

The example below illustrates the issue:
  1. Go to the Admin > Attributes > User tab.
  2. Create a few separators (Edit > Add Separator button) and divide the existing attributes among the separators. In this example, five separators have been created in the following order:
  1. Identifiers
  2. Basic
  3. Company
  4. Dates
  5. Other
User-added image
  1. Save the changes. Note the sequence of separators has been changed to:
  1. Basic
  2. Company
  3. Dates
  4. Identifiers
  5. Other
  User-added image
 
  1. At first, the User details page (Users > Users > {user name} > General tab) shows the correct order as set earlier:
  1. Identifiers
  2. Basic
  3. Company
  4. Dates
  5. Other 
 
User-added image
  1. Go to the Admin > Attributes > Users tab again and make a change. For example, make one of the attributes public and save your changes.
  2. View the Users details page again (Users > Users > {user name} > General tab) and note the order has now been incorrectly changed to:
  1. Basic
  2. Company
  3. Dates
  4. Identifiers
  5. Other
 
User-added image

 
Cause
This is a known issue reported in engineering ticket ACM-79532.
 
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • RSA Identity Governance & Lifecycle 7.1.0 P09
  • RSA Identity Governance & Lifecycle 7.1.1 P03
  • RSA Identity Governance & Lifecycle 7.2.0
Don't see what you're looking for?