on Jan 21, 2020Article Content
| Article Number | 000038365 |
| Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.0.x, 7.1.x |
| Issue | A change request to remove an Aveksa Application or Directory entitlement shows as completed yet the access still shows on the user's access tab (Users < Users < {user name} > Access tab.) In the following example, a request to remove the Aveksa Application: Exceptions Manager entitlement from a user was completed but the access was not removed from the user.   |
| Cause | When a user is assigned to an Application or a Directory as a Business Owner, Technical Owner, or Violation Manager, they are automatically assigned the required Aveksa Application/Directory entitlement(s) for these roles. This issue occurs if the required entitlement(s) is removed from the user without removing them as the Business Owner, Technical Owner, or Violation Manager of the Application/Directory. The fact that the change request shows the access has been removed when it has not been removed has been reported in engineering ticket ACM-103280. |
| Resolution | The proper way to remove this type of access from a user is to reassign their role as a Business Owner, Technical Owner, or Violation Manager to another user. It does not make sense to remove the access directly since the user requires this access to be a Business Owner, Technical Owner, or Violation Manager. This issue is being investigated by the Engineering team in order to provide a permanent resolution in a future release. |
| Workaround | To remove the Aveksa applilcation access associated with the Business Owner, Technical Owner, and Violation Manager roles, determine which Application/Directory to which the user is assigned as one of these roles and reassign the role to another user. For example, to resolve the example presented in this RSA Knowledge Base Article:
|