• Type: Bug
• Resolution: Unresolved
• Priority: Medium (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 8.10.0, 8.12.2, 8.13.1, 8.20.0, 8.20.3
• Component/s: User Management - Groups , User Management - LDAP Integration
• Labels:

  • lts813
  • raid
  • warranty

1. 

   image-2020-09-24-17-39-03-135.png

   679 kB

   24/Sep/2020 12:09 PM

[JRASERVER-71476] LDAP users and groups starting with #, & special characters are not returned in user picker fields

Collapse comment: fvinhas added a comment - 15/Aug/2022 1:53 PM

fvinhas added a comment - 15/Aug/2022 1:53 PM

I have same problem, upgrade Jira Datacenter version 8.22.6 and users login error with nested groups with special character # in dn

Expand comment: fvinhas added a comment - 15/Aug/2022 1:53 PM

fvinhas added a comment - 15/Aug/2022 1:53 PM I have same problem, upgrade Jira Datacenter version 8.22.6 and users login error with nested groups with special character # in dn

Collapse comment: Ben Szmyt added a comment - 09/May/2022 11:05 PM

Ben Szmyt added a comment - 09/May/2022 11:05 PM

What other things could you search for in the group to bring up a result? Is there  work around for this? I am having the same issue and cannot figure it out.

Expand comment: Ben Szmyt added a comment - 09/May/2022 11:05 PM

Ben Szmyt added a comment - 09/May/2022 11:05 PM What other things could you search for in the group to bring up a result? Is there  work around for this? I am having the same issue and cannot figure it out.

Collapse comment: Nathan Neulinger added a comment - 16/Dec/2020 8:54 PM

Nathan Neulinger added a comment - 16/Dec/2020 8:54 PM

Note that at the very least - the role add UI is not properly encoding it's submitted request - if you search for &test you wind up seeing &test in the raw URL instead of the URI-encoded value. Even if the underlying bug with the list results isn't fixed, that needs corrected.

In my case, I was able to compensate by searching for something else in the group name that let it be returned.

Expand comment: Nathan Neulinger added a comment - 16/Dec/2020 8:54 PM

Nathan Neulinger added a comment - 16/Dec/2020 8:54 PM Note that at the very least - the role add UI is not properly encoding it's submitted request - if you search for &test you wind up seeing &test in the raw URL instead of the URI-encoded value. Even if the underlying bug with the list results isn't fixed, that needs corrected. In my case, I was able to compensate by searching for something else in the group name that let it be returned.

Collapse comment: Tibor Marchyn added a comment - 24/Sep/2020 9:49 AM, Edited by Tibor Marchyn - 24/Sep/2020 9:49 AM

Tibor Marchyn added a comment - 24/Sep/2020 9:49 AM - edited

Same applies for "&" character. "&" is processed on backend as wildcard but not showing groups with "&" in name. Example is group named "R&D". When admin type "R" it started to filtering groups, but when type "R&" it show same results as "R", but still group named "R&D" not showed in user/group picker in project roles. It's critical as there is no workaround, neither renaming group is possible or replacing by alternative groups.

 

Not working from version 8.9.0

Expand comment: Tibor Marchyn added a comment - 24/Sep/2020 9:49 AM, Edited by Tibor Marchyn - 24/Sep/2020 9:49 AM

Tibor Marchyn added a comment - 24/Sep/2020 9:49 AM - edited Same applies for "&" character. "&" is processed on backend as wildcard but not showing groups with "&" in name. Example is group named "R&D". When admin type "R" it started to filtering groups, but when type "R&" it show same results as "R", but still group named "R&D" not showed in user/group picker in project roles. It's critical as there is no workaround, neither renaming group is possible or replacing by alternative groups.   Not working from version 8.9.0