User-type user attributes show internal ID values instead of UserID values in RSA Identity Governance & Lifecycle
Originally Published: 2018-01-03
Last Modified: 2023-09-25
Article Number
Applies To
RSA Version/Condition: 7.0.2
Issue
For example:
- Create or use any user data type attribute to collect values for the attribute. In this example, we have created a new custom user data type attribute and set data source as Managed.
- Pick any user from the Users > Users tab and click Edit Attributes.
- Find the New supervisor attribute and select any user as the New supervisor. In this example, we are making AveksaAdmin the New supervisor for the RSA User.
- Click OK and the New Supervisor attribute will have the username of AveksaAdmin.
- Go back to the Users > Users tab and the value for New supervisor will be 0 instead of AveksaAdmin. This is because the application resolves to the internal ID of AveksaAdmin:
- We can confirm the internal ID of the AveksaAdmin from the URL:
Cause
Resolution
Related Articles
RSA Identity Governance and Lifecycle NullPointerException when rules associated with Attribute Synchronization run 172Number of Views Is SHA-256 supported on RSA_CM with a HSM via P11? 29Number of Views 'WFLYDM0085: The alias specified 'server' does not exist in the KeyStore' error in RSA Identity Governance & Lifecycle 293Number of Views How to map the value of a Microsoft Active Directory object to a RADIUS user attribute definition to be associated to a RA… 203Number of Views How to use the ASR to determine if 100% CPU Usage, Out of Memory Issues, and Periodic System Unresponsiveness are caused b… 228Number of Views
Trending Articles
Don't see what you're looking for?