Usernames are case sensitive
Description
Environment
None
Attachments
2
Checklists
QAlity Plus - Test Management
Activity
Show:
Joanna Bebak December 20, 2017 at 1:12 PM
I checked, and the issue with the UI no longer occurs, so I will close the ticket.
Sebastian Brudziński December 20, 2017 at 1:03 PM
This is now fixed.
Joanna Bebak December 20, 2017 at 9:30 AM
After Sebastian's investigation, it turned out that the UI issue can be fixed as a part of this ticket.
Joanna Bebak December 20, 2017 at 8:50 AM
All right. Please let me know when you have investigated the issue and tell me whether I should close this ticket or not.
Sebastian Brudziński December 20, 2017 at 8:47 AM
If it's not causing any issues, I wouldn't worry about this. But I can take a look if that can be easily changed.
Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Sebastian BrudzińskiReporter
Nick ReidStory Points
5
Original estimate
Time tracking
Components
Sprint
None
Fix versions
Priority
MinorTime Assistant
Open Time Assistant
Time Assistant
Open Time Assistant
Created November 3, 2017 at 9:20 PM
Updated November 22, 2020 at 1:55 PM
Resolved December 20, 2017 at 1:12 PM
User names are case sensitive, which is not a standard practice in any software. This could cause usability problems down the road.
This means that a user "Test" would not be able to successfully login with the username "test"
This should be enforced in both the services and UI
Steps to reproduce:
log as admin -> success
log as AdMiN -> fail
Acceptance Criteria
Make username unique at the database level so case sensitivity doesn't matter
A person can login if their username is "administrator" and they login with "Administrator"
No changes should be made to UI code