-
Bug
-
Resolution: Fixed
-
Medium
-
4.4.3
-
4.04
-
This issue directly relates to JRA-24558, which has been marked fixed for JIRA 4.4.3.
- Create a user in LDAP with mix case and have your connector directory synchronized in JIRA
- Now create an issue security scheme with security level restrricted to Assignees and reporters only
If the mix case user from LDAP creates an issue, he will be the reporter but he will still be restricted from viewing or searching the issue in the navigator or the project browser. He can however view the issue on visiting the issue url directly. This is not the case with internal users.
As a result of this, users are not able to implement the issue security scheme
- is cloned from
-
JRASERVER-26194 Mixed case username from LDAP still has a few problems
- Closed
- is related to
-
JRASERVER-27600 Mixed case username from LDAP causes problems in subscriptions
- Closed
- relates to
-
JRASERVER-24558 JIRA using mixed-case username from LDAP corrupt other features
- Closed
-
JRASERVER-29054 JIRA using mixed-case username from LDAP
- Closed
-
JRASERVER-26441 Mixed case username from LDAP doesn't match existing Dashboards
- Closed
-
JRASERVER-27601 Mixed case username causes problems with UserHistory
- Closed
-
JRASERVER-30247 Getting 'duplicate key' database error when trying to look at a user's profile page.
- Closed