Resurrecting this thread. . .
I think I'm misunderstanding where we landed on this issue. On the one
hand, it seems like there are tests to assert that uniqueness of names is
case-sensitive. On the other, some folks have identified reasons why they
would want case-insensitivity on uniqueness
On Thu, Sep 26, 2013 at 11:02:22AM -0500, Brant Knudson wrote:
On Thu, Sep 26, 2013 at 4:44 AM, Ralf Haferkamp rha...@suse.de wrote:
[..]
My recommendation is that Keystone should get away from dealing with
creating/updating users to avoid reinventing the wheel (and making a wheel
that's
On Wed, Sep 25, 2013 at 09:45:32AM +0100, Henry Nash wrote:
Hi
Do we specify somewhere whether text field matching in the API is case
sensitive or in-sensitive? I'm thinking about filters, as well as user and
domain names in authentication. I think our current implementation will
always
On Thu, Sep 26, 2013 at 11:02 AM, Brant Knudson b...@acm.org wrote:
On Thu, Sep 26, 2013 at 4:44 AM, Ralf Haferkamp rha...@suse.de wrote:
As Dolph already suggested we should not allow usernames that just differ
in
capitalization (JDoe vs. jdoe) to co-exist. (Which could be an
argument
Excerpts from Henry Nash's message of 2013-09-25 01:45:32 -0700:
Hi
Do we specify somewhere whether text field matching in the API is case
sensitive or in-sensitive? I'm thinking about filters, as well as user and
domain names in authentication. I think our current implementation will
Hi
Do we specify somewhere whether text field matching in the API is case
sensitive or in-sensitive? I'm thinking about filters, as well as user and
domain names in authentication. I think our current implementation will always
be case sensitive for filters (since we do that in python and
On Wed, Sep 25, 2013 at 3:45 AM, Henry Nash hen...@linux.vnet.ibm.comwrote:
Hi
Do we specify somewhere whether text field matching in the API is case
sensitive or in-sensitive? I'm thinking about filters, as well as user and
domain names in authentication. I think our current
