You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the check for cyclic group membership happens when Authorizable.addMember(...) is called (and not only after commit()) the order of addMember(...) and removeMember(...) matters. The latter should be called first on all managed authorizables to prevent the "Cyclic group membership" exception which may happen when a group has been fundamentally changed.
The reproduce the issue with 2.5.2 just create the following group memberships first
group 1 -> group 2 -> group 3
establish that membership in the ACTool and then change via config to group 2 -> group3 -> group1
The text was updated successfully, but these errors were encountered:
As the check for cyclic group membership happens when
Authorizable.addMember(...)
is called (and not only aftercommit()
) the order ofaddMember(...)
andremoveMember(...)
matters. The latter should be called first on all managed authorizables to prevent the "Cyclic group membership" exception which may happen when a group has been fundamentally changed.The reproduce the issue with 2.5.2 just create the following group memberships first
group 1 -> group 2 -> group 3
establish that membership in the ACTool and then change via config to
group 2 -> group3 -> group1
The text was updated successfully, but these errors were encountered: