A change request to remove role access from a user tries to remove AD group (indirect access from role) which no longer exists as user access causing errors in RSA Identity Governance & Lifecycle
Originally Published: 2019-04-23
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
Issue
Scenario
User accounts belonging to AD groups are later given access to the same AD groups via a role.A termination rule to trigger for terminated users with action to disable and delete the accounts will trigger when the user is terminated.
If you try to remove the access to role, the change request also tries to remove the indirect AD entitlement and the AFX fulfillment fails with an error:
Cause
Resolution
This issue is fixed in 7.0.2 P14, 7.1.0 P07, and 7.1.1 P01.
Related Articles
A change request to remove role access from a user tries to remove AD group (indirect access from role) which no longer ex… 59Number of Views How to use RSA Mobile Administration API 12Number of Views A completed change request to remove Aveksa Application/Directory entitlements from a user does not remove the access from… 208Number of Views How to manual deploy Federated Identity Manager (FIM) 2.5 / 2.6 10Number of Views How to run the RegisterUserExample Admin API example code in RSA Mobile Authentication Server 1.5 4Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?