-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.4.2, 9.12.15, 10.2.0, 10.3.0
-
Component/s: Jira 10.3 EAP, User Management - Groups , User Management - LDAP Integration
-
None
-
9.04
-
1
-
Severity 2 - Major
-
1
Issue Summary
When updating a Delegated LDAP directory it does not accept a blank value on Default Group Memberships if any value is already set, it only accepts another string.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- In a Jira instance add a Delegated LDAP directory with any value in Default Group Memberships.
- Try to edit the directory leaving the Default Group Memberships blank.
Expected Results
Directory updated with blank value in Default Group Memberships
Actual Results
It reloads the same value.
Workaround
Workaround 1:
- Create a second directory with similar values inserted, but leaving the Default Group Memberships and marking to Update User attributes on Login
- Move the newly created directory to a higher rank than the old
- Deactivate the old directory after the users login again (so correcting the reference in Jira).
Attention, carefully proceed with this workaround, and only deactivate the old directory after all users login, once (if deactivating first) in Admin > User Management the users will not be available until login again and the reference in issues will point to users with no info.
Workaround 2:
- Create a dummy group that does not grant any permission to the user.
- Instead of removing the group from the directory configuration, replace with this dummy group.
- is related to
-
JRASERVER-75035 When using Delegated LDAP with default group, the group membership is not populated
-
- Long Term Backlog
-