cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10394) Mixed case usernames do not work
Date Fri, 09 Oct 2015 17:13:05 GMT


Tyler Hobbs commented on CASSANDRA-10394:

I'm +1 on the patch.  I think it's better to fix the {{CREATE ROLE}} behavior to match the
old {{CREATE USER}} behavior for string literals (which is probably an uncommon usage, anyway)
than to preserve the behavior indefinitely.

As a nitpick on the tests: can you add a test case to ensure that a case-sensitive user/rolename
_doesn't_ work with the wrong case?

> 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