keystoneclient token-get should work with --token/SERVICE_TOKEN
Bug #1002917 reported by
Dolph Mathews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Currently, running token-get fails because a service catalog isn't retrieved by the client:
$ keystone --token=ADMIN --endpoint=http://
'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://
+--
| Property | Value |
+--
| id | ADMIN |
+--
Changed in keystone: | |
status: | New → In Progress |
Changed in keystone: | |
status: | In Progress → Confirmed |
assignee: | Dolph Mathews (dolph) → nobody |
To post a comment you must log in.
I think, it's because the client is authenticated only if endpoint is not specified. If endpoint is specified, it's not authenticated and in turn service_catalog is not set.
Snippet from v2_0/client. py:Client. __init_ _(), line 79:
if endpoint is None:
self. authenticate( )
self. management_ url = endpoint
else:
To get the token, I think we should authenticate explicitly using specified token and/or user/pass.
Dolph, can you please confirm?