-
Suggestion
-
Resolution: Fixed
-
None
CWD-74 will provide nested group support for LDAP directories, but not for internal directories.
Internal directories should be able to be nested for administration purposes.
[CWD-980] Add Nested Groups for Internal Directories
David O'Flynn [Atlassian]
added a comment - Yep, it'll work for delegated as well as internal.
And no, it can't be fixed prior to 2.0. Sorry 
It's quite a bit of work.
David O'Flynn [Atlassian]
added a comment - Yep, it'll work for delegated as well as internal.
And no, it can't be fixed prior to 2.0. Sorry It's quite a bit of work. 
Andrew G Howell
added a comment - David,
I agree w/ Justin, would like verifiation that this will be supported in Delegated Directories as well. Even better if it can be fixed prior to 2.0. You give a mouse a cookie...
Andrew G Howell
added a comment - David,
I agree w/ Justin, would like verifiation that this will be supported in Delegated Directories as well. Even better if it can be fixed prior to 2.0. You give a mouse a cookie... David - can you confirm that this will also apply to Delegated Directories? It seems like it would (as Delegated Directories as basically Internal Directories as far as groups go), but some confirmation would be good.
David O'Flynn [Atlassian]
added a comment - Hi Kevin,
2.0 will be the next major release of Crowd (there'll be a 1.6.1 to fix a couple of long-standing bugs that missed 1.6). We'll get it out as soon as we can
Cheers,
Dave.
David O'Flynn [Atlassian]
added a comment - Hi Kevin,
2.0 will be the next major release of Crowd (there'll be a 1.6.1 to fix a couple of long-standing bugs that missed 1.6). We'll get it out as soon as we can
Cheers,
Dave. 
Kevin Ross
added a comment - We are just implementing crowd and somehow I missed the fact that an internal directory cannot have nested groups. I must have been reading about a directory representation of an external LDAP.
The primary reason we decided to switch to crowd was the amount of effort we must exert to manage confluence spaces, jira project permissions and SVN access in our varied environment. We have internal operational staff, developers, managers, then we have the same from our development partners (slightly different permissions), and yet a different set of permutations with customers (they use all of the above as well).
We have only been using the jira database for authentication (with the exception of SVN), and when we decided to add fisheye, bamboo, and crucible to the mix it was definitely too much not to use crowd.
I see this on the roadmap for 2.0, but I'm hoping that my vote and this comment may be some fuel to expedite the implementation sooner rather than later.
Even if this might be available as an unsupported patch, we would be happy to try it out.
Kevin Ross
added a comment - We are just implementing crowd and somehow I missed the fact that an internal directory cannot have nested groups. I must have been reading about a directory representation of an external LDAP.
The primary reason we decided to switch to crowd was the amount of effort we must exert to manage confluence spaces, jira project permissions and SVN access in our varied environment. We have internal operational staff, developers, managers, then we have the same from our development partners (slightly different permissions), and yet a different set of permutations with customers (they use all of the above as well).
We have only been using the jira database for authentication (with the exception of SVN), and when we decided to add fisheye, bamboo, and crucible to the mix it was definitely too much not to use crowd.
I see this on the roadmap for 2.0, but I'm hoping that my vote and this comment may be some fuel to expedite the implementation sooner rather than later.
Even if this might be available as an unsupported patch, we would be happy to try it out.
Bob Swift
added a comment - - Another use case is to be able to add groups to a delegated directory that merge multiple groups. For instance, I have a group from AD that is imported and re-imported to keep it current with AD. Now I want another group that is a merge of the AD group together with some additional users and/or other groups.
- Another case is I want to continue to use confluence-users but now I just want it to all the users in one (or more) groups in the delegated directory (again, it gets automatically updated on the next import).
Bob Swift
added a comment -
Another use case is to be able to add groups to a delegated directory that merge multiple groups. For instance, I have a group from AD that is imported and re-imported to keep it current with AD. Now I want another group that is a merge of the AD group together with some additional users and/or other groups.
Another case is I want to continue to use confluence-users but now I just want it to all the users in one (or more) groups in the delegated directory (again, it gets automatically updated on the next import).
This has been implemented for both Internal Directories and Delegated Directories.