[MAGNOLIA-2044] Groups are not resolved properly with ExternalUser Created: 05/Feb/08  Updated: 23/Jan/13  Resolved: 05/Feb/08

Status: Closed
Project: Magnolia
Component/s: core, security
Affects Version/s: 3.5.4
Fix Version/s: 3.5.5

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1787 Refactoring of GroupList/RoleList int... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

because the RoleList interface extends the GroupList interface, when doing subject.getPrincipals(GroupList.class) you might get the list of roles instead of the groups.
This prevents, for instance, getting the workflow items assigned to an ldap-user's groups.



 Comments   
Comment by Magnolia International [ 05/Feb/08 ]

done; xtracted PrincipalList/AbstractPrincipalList to avoid that RoleList extends GroupList.

Generated at Mon Feb 12 03:32:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.