yahoo-eng-team team mailing list archive

[Steve Martinelli <stevemar@xxxxxxxxxx>]

sorry dolph, as you have told me many times, the admin token itself
carries no authorization. if you disagree open a bug against
openstackclient to have this as a client specific feature, keystone
server shouldn't change the way it's handled

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1002917

Title:
  keystoneclient token-get should work with --token/SERVICE_TOKEN

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

Bug description:
  Currently, running token-get fails because a service catalog isn't
  retrieved by the client:

      $ keystone --token=ADMIN --endpoint=http://localhost:35357/v2.0/ token-get
      'Client' object has no attribute 'service_catalog'

  While I think token-get should attempt to validate the specified
  token, it should at least echo it back instead of spewing an error
  message, e.g.:

      $ keystone --token=ADMIN --endpoint=http://localhost:35357/v2.0/ token-get
      +----------+-------+
      | Property | Value |
      +----------+-------+
      | id       | ADMIN |
      +----------+-------+

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