Multiple roles stuck in applied state after applying bulk change on multiple roles in RSA Governance & Lifecycle
Last Modified: 2024-12-09
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 Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle 126Number of Views Multi-App Collector Circuit Breaker trips incorrectly in SecurID Governance & Lifecycle 209Number of Views Terminated Users not correctly removed from Roles in RSA Identity Governance & Lifecycle 115Number of Views Entitlements are removed from or added to a Role when the Role Set is changed in RSA Identity Governance & Lifecycle 243Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?