Multiple roles stuck in applied state after applying bulk change on multiple roles in RSA Governance & Lifecycle
Article Number
Issue
After applying bulk changes on multiple roles involved in one request at the same time.
The request completes, but the roles are stuck in applied state.
Cause
If the system is restarted during the creation of change requests related to the Role changes it may leave the Role in applied state.
Bulk Role changes create workflow watches that keep monitoring the CR completion delete the role_id from t_av_roleversion when the change request is completed. If the system gets restarted the watches may not be cleared.
Resolution
Note:- user must take a backup from below query
select cr.id,cr.name,rv.* from t_av_roleversions rv join t_av_change_requests cr on rv.cr_id=cr.id where rv.state='A' and cr.current_state='CO' order by cr.id;
Related Articles
Roles stuck in Applied state in SecurID Governance & Lifecycle 384Number of Views After refreshing a user access review, the business source values for roles (role sets) display as null in RSA Identity Go… 30Number of Views List of Trusted Certificate Authorities for HFED and Trusted Headers Applications 74Number of Views install the enterprise co-ordinator hangs at end when communication with the data base has access to firewall ...sees the … 14Number of Views Role appears in a "Changed" state during Role Review even after undoing all actions in RSA Governance & Lifecycle 4Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?