Case-Insensitivity in keystone¶

Users¶

If a user with the name “MyUser” already exists, then the following call which creates a new user by the name of “myuser” will return a 409 Conflict:

POST /v3/users {name: myuser}

Projects¶

If a project with the name “Foobar” already exists, then the following call which creates a new project by the name of “foobar” will return a 409 Conflict:

POST /v3/projects {name: foobar}

Roles¶

Role names are case-insensitive. for example, when keystone bootstraps default roles, it creates “admin”, “member”, and “reader”. If another role, “Member” (note the upper case ‘M’) is created, keystone will return a 409 Conflict since it considers the name “Member” equivalent to “member”. Note that case is preserved in this event.

MySQL & SQLite¶

By default, MySQL/SQLite are case-insensitive but case-preserving for varchar. This means that setting a project name of “mYpRoJeCt” will cause attempting to create a new project named “myproject” to fail with keystone returning a 409 Conflict. However, the original value of “mYpRoJeCt” will still be returned since case is preserved.

Users will be treated the same, if another user is added with the name “myuser”, keystone will respond with 409 Conflict since another user with the (same) name exists (“mYuSeR”).

PostgreSQL¶

PostgreSQL is case-sensitive by default, so if a project by the name of “myproject” is created with the existing “mYpRoJeCt”, it will be created successfully.

LDAP¶

By default, LDAP DNs are case-insensitive, so the example with users under MySQL will apply here as well.