As documented in the Crowd 2.1 Upgrade Notes, the username and group memberships for the user are always obtained from the same directory. Therefore the group memberships are not aggregated across directories any more.
Would be very useful to have this functionality back, through an UI option that would allow group memberships to be aggregated across directories.
- is duplicated by
-
CWD-2592 This is a Major Priority "Bug" and affects backward compatibility that you still didn't fix
-
- Closed
-
-
CWD-2618 How can I undo the changes to Crowd 2.1 that cause crowd to no longer "amalgamated the group memberships"
- Closed
-
- Closed
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
- relates to
-
-
[CWD-2135] Add option that would allow group memberships to be aggregated across directories again
Hi dunterwurzacher, any news about this one? Will this be applied on JIRA as well, or the decision to prevent it is still valid? Could we have some justification about it if true?
dunterwurzacher This is great. Thanks for the Just hoping to see this soon on JIRA as well.
Hi angel6, dberrueta and jwalton, no need to raise more requests, this functionality is already in Confluence as of 5.7, and Stash as of 3.4. Currently aggregation is enabled by default, and can only be disabled by hitting a REST endpoint, as there's currently no UI to manage the aggregation semantics. EMBCWD-961 is actually just the request to add a UI checkbox to change the semantics.
The docs for how it works in Confluence, and how to disable it, are here.
For Stash, the docs are here.
This functionality is not currently available in JIRA, but this has been a conscious choice. I'm talking with the team to get an official answer about whether it will be brought into JIRA at some point, or if there's a way to enable it, and I'll get back to you as soon as I can. Thanks for your patience.
angel6 yes; that's right, separate JIRA and Confluence issues. There is shared code. However, the PMs on those teams are better placed to judge customer requirements and priority here.
jwalton, so you suggest creating respective issues for JIRA, Confluence etc. right? I had the impression that embedded crowd was integrated into other Atlassian products on a regular base to bring new features and improvements to them as well.
angel6 yes, that's an internal project. If you're interested in having this in other products then that is best tracked through issues filed against those products so they can consider it in their specific case.
Sorry angel6, I linked an internal issue. I think EMBCWD-961 is equivalent to this issue (CWD-2135), and unfortunately it is not fixed yet. I'll keep CWD-2135 open so you can keep track of the progress on this feature.
dberrueta Sorry I don't have the right permissions to see EMBCWD-961. If it says that this particular feature is also available in embedded Crowd, then this is it. Is so, is it already fixed or pending?
As of JIRA 6.4, group memberships are still not aggregated across directories. ben4 are you able to provide more context around the decision for JIRA?