Closed
Bug 564199
Opened 15 years ago
Closed 15 years ago
server should lowercase account names when creating users
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hans, Assigned: telliott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
When I try to login to my personal Weave server (where my username is "Spone"), Weave Sync fails to log me in.
I changed my username to "spone" and it works well.
I don't know if this is the Weave Sync add-on that sanitizes the login to lowercase, or if the Weave Server is deficient.
My server runs Linux. My PC runs Windows 7.
Reproducible: Always
Steps to Reproduce:
1. try to login to your Weave server using Weave Sync with a case-sensitive username. It fails.
2. change your username on your server to remove uppercase
3. try to login with the news lowercase username. It works.
Comment 1•15 years ago
|
||
We lowercase all user names in the client, by design. Because Weave relies on URL syntax, it causes problems.
https://<server>/1.0/mconnor/storage/meta/global
vs.
https://<server>/1.0/Mconnor/storage/meta/global
Moving this to Server, I think the LDAP version handles this, but maybe the minimal server create script doesn't?
Assignee: nobody → telliott
Component: Sync → Server
QA Contact: sync → server
Summary: can't connect to my Weave server with a case-sensitive login → server should lowercase account names when creating users
Assignee | ||
Comment 2•15 years ago
|
||
Somehow, this bug wasn't showing right in my queue. We did this some time ago - the server automatically lowercases all usernames in the url and the basic-auth before doing anything with them
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•