cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10394) Mixed case usernames do not work
Date Thu, 24 Sep 2015 17:04:04 GMT


Sam Tunnicliffe commented on CASSANDRA-10394:

The fix is simple, I'd just incorrectly set the {{keepCase}} flag, so I've pushed patches
reversing that. Incidentally, the new (in 2.2) {{CREATE ROLE}} syntax was behaving in the
same way. Of course, that isn't technically a regression but I do think it's probably not
what most users will be expecting so I've also changed that to preserve the case. That's perhaps
a bit controversial for a minor release, so I'd be ok with omitting that part.


CI Tests:
| [dtests|]|
| [dtests|]|
| [dtests|]|

> Mixed case usernames do not work
> --------------------------------
>                 Key: CASSANDRA-10394
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Centos 7, Cassandra 2.2.1
>            Reporter: William Streaker
>            Assignee: Sam Tunnicliffe
>            Priority: Critical
>             Fix For: 2.2.x
> When you create a user with a mixed case username it is stored as all lower case.  When
you try and login with the mixed case username it will fail, but logging in as the lower case
name works.   This is a change from the 2.1.x versions that are released where mixed case
usernames worked.
> example:
> CREATE USER stBarts WITH PASSWORD 'island';   
> The above statement changes the username to "stbarts".
> This would not be so bad except during login case does matter and has to match what is
stored in the system.   
> Recommended fix: allow mixed case usernames to be stored in system, or convert mixed
case username entered to lower case during login.

This message was sent by Atlassian JIRA

View raw message