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
Sub-groups resolution is rejected and Member Type is set to "Account" instead of "Group" for Account Collectors in RSA Ide… 43Number of Views Is SHA-256 supported on RSA_CM with a HSM via P11? 29Number of Views Authentication to remote Active Directory fails in RSA Governance and Lifecycle when auto select is unchecked 45Number of Views View User Aliases Associated with a RADIUS Profile 9Number of Views RSA Governance & Lifecycle 8.0 Patch 03 Release Notes 103Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?