-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.0.10, 7.1.8, 7.2.7, 7.4.0, 7.3.1, 7.13.0
-
7
-
37
-
Severity 3 - Minor
-
6
-
Summary
In the logs, the error are still thrown regarding the mixed case group names on LDAP side (JRA-36424), however, no impact on functionality wise
Steps to Reproduce
- Add a new user from Active Directory.
- Synchronise that user.
- Change one of the groups the user belongs to to uppercase, e.g.: change Ninja-Superstar to ninja-superstar.
- Attempt to login.
Expected Results
The user logs in without any worries. No logs/warning are thrown
Actual Results
User functionality not impacted.
However, in logs, following are thrown and groups are not updated with name changes.
The below exception is thrown in the xxxxxxx.log file:
2016-07-28 09:33:52,402 Caesium-1-4 WARN ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] remote group name [ JR_test ] casing differs from local group name [ JR_TEST ]. Group details will be kept updated, but the group name cannot be updated
- relates to
-
JRASERVER-36424 Mixed case group names breaks the connection between JIRA and LDAP for User Management
- Closed
-
JRASERVER-29025 Mixed case usernames breaks the connection between JIRA and LDAP for User Management
- Closed
-
JRASERVER-35309 Updating the Lower Case Output option in crowd does not affect group names in JIRA
- Gathering Impact