Unable to re-edit a RSA Identity Governance & Lifecycle condition containing IN for a rules definition
Originally Published: 2018-03-02
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.0.2, 7.1
Issue
However, when the condition is re-edited, there is no IN clause and in Advanced mode, the Where Clause textbox is empty.
This results in the IN clause needing to be re-entered.
Cause
Resolution
Workaround
Advanced Mode
Manually enter the IN clause as a set of OR statements instead. For example, change:approles.name in ('Access Request Administrator','Application Administrator')
to:
approles.name = 'Access Request Administrator' OR approles.name = 'Application Administrator'
Please note that there is a maximum limit of 4000 characters.
Simple Mode
Alternately, do not use Advanced Mode, use Simple Mode.- Click on the object to be included:
- Select the object values from the picklist and click OK.
Related Articles
AM8.1-Web tier Bootstrap service will not start after re-install 95Number of Views Disaster recovery - Re-imaging a RC 96Number of Views RSA Identity Governance & Lifecycle server attempts to apply the patch each time with the message "Patch will be (re-)appl… 37Number of Views Access Manager CERTIFICATE authentication fails to re-authenticate after token decryption failed message 92Number of Views How to re-use unassigned tokens via the 'Replace Tokens...' function on Authentication Manager 6.x 9Number of Views
Trending Articles
Authentication Manager Supported Hardware and Upgrade Paths RSA Authentication Manager Upgrade Process Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager 'Principal Does Not Possess Authenticator' Error for Users with Multiple IDs
Don't see what you're looking for?