-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
If an application has lowerCaseOutput set then it will never receive mixed-case names.
When user details posted to the '/user' resource are checked to make sure the payload entity matches the username in the database this is currently a case-sensitive check, which fails because the returned lowercase output doesn't match the mixed case stored in Crowd.
For consistency with Crowd's case-insensitive, case-preserving behaviour this check should also be case-insensitive. The update shouldn't affect the existing case in the database.
[CWD-3307] Usernames in updates posted to /user should be checked case-insensitively
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510782 ] | New: JAC Bug Workflow v3 [ 3365276 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391512 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510782 ] |
Workflow | Original: Crowd Development Workflow v2 [ 530902 ] | New: Simplified Crowd Development Workflow v2 [ 1391512 ] |
Remote Link | New: This issue links to "Wiki Page (Extranet)" [ 42817 ] |
Fix Version/s | New: 2.6.3 [ 32491 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Technical Review [ 10028 ] | New: Resolved [ 5 ] |
Status | Original: In Progress [ 3 ] | New: Technical Review [ 10028 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Rank | New: Ranked higher |
Sprint | New: Sprint 23 [ 516 ] |