-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.11.2, 8.2.3, 7.13.6
-
7.11
-
3
-
Severity 3 - Minor
-
0
-
Issue Summary
Adding the same user group from local and active directory causes unexpected results. Variation on this can occur using the same name but with one letter cased differently.
Steps to Reproduce
- add at least one active directory in Jira's User Directories
- create a local group, for example 'Production'. Add a global share permission to the group, in Jira.
- create a group in the added User Directory, for example 'production', add some users to it
Expected Results
The groups are seen separately in Jira and function independently. Global share permission can be removed or added to each group.
Actual Results
The groups are merged. The local user memberships are no longer visible.
Also some functionalities like removing global share permissions can no longer be controlled (as removing fails silently).
Workaround
Global share permission can be removed from database directly, for example:
DELETE FROM public.globalpermissionentry WHERE PERMISSION='CREATE_SHARED_OBJECTS' AND GROUP_ID='jira-test'
Notes
see also:
- https://jira.atlassian.com/browse/JRASERVER-66032 (when using same group name)
- https://jira.atlassian.com/browse/JRASERVER-66599 (when using same group name + space)
- is related to
-
JRASERVER-66599 LDAP group can't be added during login due to duplicate key row
- Gathering Impact
-
JRASERVER-66032 Group is not updated in certains scenario
- Gathering Impact