-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.3.3, 6.1.7, 6.2, 6.2.4, 6.4.1, 6.4.4
-
Tested with Microsoft Active Directory > OpenDS
-
4.03
-
41
-
Severity 3 - Minor
-
2
-
Putting internal group into external groups, or vice versa or putting external group into external group, all does not work, even when authenticating with LDAP by the LDAP root user and using read/write permissions in the LDAP directory configuration. It always ends up with the error:
You do not have permission to perform this operation.
Suggestion:
If this feature is only meant to work for internal directories groups, we should:
- Have clearer error message on the problem (as it is not a permission issue here)
- Make it clear in our documentation that this feature is only for internal directories groups
- In the list of groups in the nested groups configuration page, there is no purpose (and it is rather misleading) to include non-internal directories groups when they will never work.
Regards,
Ali
Atlassian Support
- is related to
-
JRASERVER-47271 LDAP User will only inherit the first nested group relationship
- Closed
-
JRASERVER-26813 Permissions are broken with nested groups
- Gathering Impact
- relates to
-
JRASERVER-59674 Nested Group Relations are not Recognized for New Directories
- Gathering Impact
-
JRASERVER-32948 Update 'Managing Nested Groups' page regarding Internal vs External groups
- Closed
-
CWD-3089 Allow remote groups as children of local groups when managing groups locally in a syncing directory (Connector)
- Closed
- mentioned in
-
Wiki Page Loading...