yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

I am marking this as "wont fix" only because we cannot fix this without
being API incompatible. I agree that the UX could be better, but it is
just not possible to correct the behavior without potentially breaking
real deployments.

** Changed in: keystone
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1379952

Title:
  API accepts tenant name for "TenantId", fails, and provides not
  helpful message

Status in OpenStack Identity (Keystone):
  Won't Fix

Bug description:
  When authenticating with Keystone's REST API, if I happen to provide
  my tenant name in the TenantId field, the resulting error tells me
  that I am not authorized for that tenant, even though all the
  information (user, pass, tenant) are correct. It *should* tell me that
  I just passed invalid data into a field that expects a UUID, which, as
  a user, would tell me exactly what was wrong.

  For what it's worth, in debugging my auth problem, I ended up
  tcpdump'ing keystone which led to this gem of a demonstration of the
  problem:

  http://paste.openstack.org/show/4v5JtwbGNu6QhQ3K5oQ1/

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1379952/+subscriptions