-
Bug
-
Resolution: Fixed
-
Medium
-
2.7.1
-
None
-
None
Crowd should amalgamate all group memberships for the same username across multiple directories. This works when querying the members of a group, but not when querying the group memberships of a user.
This works (pseudo-code):
crowdGroup.getUsers();
This does not:
crowdUser.getGroups();
Here's the offending REST endpoint:
localhost:4990/crowd/rest/usermanagement/1/user/group/direct?username=user1&start-index=0&max-results=-1
What this can mean in downstream applications is that all groups are amalgamated when a user logs in to Confluence, but when they log in to the admin console, they only get the memberships from the top directory in Crowd. This has caused problems for users where their confluence-administrators and jira-administrators groups are in the second place directory, and logging in to the admin console means they lose these groups and authentication fails.
- is related to
-
CWD-3870 As an admin, I want to choose the membership aggregation semantics I want for each application
- Closed
-
EMBCWD-961 Loading...
- relates to
-
CWD-2135 Add option that would allow group memberships to be aggregated across directories again
- Closed
-
LEM-233 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...