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
Microsoft Exchange 2010 AFX Connector Enable-mailbox command fails with 'Value cannot be null' in RSA Identity Governance … 97Number of Views Assign a Temporary Fixed Tokencode for Online Emergency Access 101Number of Views A Firewall is blocking Remote AFX Agents and Remote Collection Agents from communicating with the Application Server in RS… 152Number of Views A completed change request to remove Aveksa Application/Directory entitlements from a user does not remove the access from… 193Number of Views RSA Authentication Manager 8.2 SP1 Vulnerabilities in Mozilla Firefox -false positive 40Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?