An extra group that's non-existed in the role added while trying to add new user to the role in RSA Governance & Lifecycle
Last Modified: 2023-10-06
Article Number
000068229
Applies To

This is a known issue in the following versions.

  • RSA Governance & Lifecycle 7.5.2
Issue
If the Role is part of the Change request and their ID matches with one of Groups Id then that Group is mistakenly considered as part of Role and it's being added to the Users, though that Group is not part of the Role.

As per the below screenshot Role x only contains "Role_Test" and no other direct or indirect entitlement

image.png

While adding any new user to Role X, Group3 is mistakenly considered as part of Role, though that Group is not part of the Role

image.png


Using the below query we can identify roles and groups with the same IDs, 
select TG.ID as group_ID,TR.ID as role_ID,TG.name as group_name, TR.name as role_name from AVUSER.T_GROUPS TG
inner join t_av_roles TR on TG.id=TR.id;

Role "Role_Test" have the same Id like "group3", accordingly Group is mistakenly considered as part of the Role
image.png
Cause
This issue occurs when Role is part of the Change request and the value of the Role_Id incidentally matches the value for Group_Id
Resolution
This issue is resolved in the following versions:
  • RSA Governance & Lifecycle 7.5.2 P06

Related Articles

Trending Articles

Don't see what you're looking for?