Running a form incorrectly filters on raw name when filtering on the Application Name attribute in RSA Identity Governance & Lifecycle
Originally Published: 2018-11-08
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2, 7.1.0
Issue
Steps to Reproduce
- Navigate to Resources > Directories.
- Select any directory. Active Directory is being used in he example below.
- Select General > Edit.
- Change Directory Raw Name to Active Directory Raw Name.
- Click OK.
- After saving the changes, note that the Directory name is changed to the Directory Raw Name.
- Edit the directory again and change the Directory name back to what it was. In this case, Active Directory.
- Note the entry in T_APPLICATIONS
- Verify that NAME (Directory Raw name, also the application name) and ALT_NAME are different.
- Go to Requests > Configuration > Request Forms > Default Password Form > Fields and click Edit next to the Account variable name.
- Click on the Account filter.
- From the drop down options choose Application Name, one of, and Active Directory Raw Name then click OK.
- Verify the information is correct in the Modify Question: Account page.
- Refresh and note that no accounts show under Select account because you have no applications with a display or alt_name of Active Directory Raw Name. This is expected.
- Click Cancel.
- Find a user with an account in Resources > Directories > Active Directory > Accounts.
- Run the form and choose the AD user (Requests > Configuration > Request Forms > Default Password Form > Fields > Run Form).
Expected Behavior
There is no Active Directory showing under Application Name because there is no Application Name called Active Directory Raw Name, which is the filter. Active Directory Raw Name is the Business Source Raw Name. This would also be consistent with the behavior in step 6.
Observed Behavior
The Active Directory directory is displayed on the form. Note when editing the form field, accounts in this directory were not shown. Now they get shown because the filter is now filtering on the alt_name field. So when you edit the field, it filters on name and when you run the form, it filters on alt_name. So when you design a form it acts one way and when you run the form it acts another way. You cannot trust your design as a result.
Resolution
Workaround
Related Articles
SecurID: Locked out of Agent host; cannot authenticate to RSA Authentication Agent for Microsoft Windows. 50Number of Views Remotely Install the Original System Image on a Dell Hardware Appliance 252Number of Views RSA Authentication Manager Restore from Microsoft Azure Snapshot or backup Failed 137Number of Views AFX Server on a WildFly cluster fails to start with 'Cannot connect to RSA Identity Governance and Lifecycle. The watchdog… 238Number of Views Can a running review be refreshed without losing the completed work in RSA Identity Governance & Lifecycle? 170Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process
Don't see what you're looking for?