Cannot get an authenticated keystone client with an existing token

Bug #1160172 reported by Steve Baker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-swiftclient
New
Undecided
Unassigned

Bug Description

A call to swiftclient.client.get_keystoneclient_2_0 will fail in the following scenario:
auth_token is set in os_options
swift endpoint is unknown so an authenticated service catalog call is required

The problem is that the auth_token is not passed to the keystone client create call, so this will only work with a password.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-swiftclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/25360

Changed in python-swiftclient:
assignee: nobody → Steve Baker (steve-stevebaker)
status: New → In Progress
Changed in python-swiftclient:
assignee: Steve Baker (steve-stevebaker) → nobody
status: In Progress → New
Revision history for this message
Chmouel Boudjnah (chmouel) wrote : Re: [Bug 1160172] Re: Cannot get an authenticated keystone client with an existing token

am I missing something?

stack@devstack:~$ swift --debug
--os-storage-url=http://127.0.0.1:8080/v1/AUTH_cd05cd5e6902440c899eaf70ce6a85a6
--os-auth-token=6886ce28003e49808997cd13898ef54b stat
DEBUG:swiftclient:REQ: curl -i
http://127.0.0.1:8080/v1/AUTH_cd05cd5e6902440c899eaf70ce6a85a6 -I -H
"X-Auth-Token: 6886ce28003e49808997cd13898ef54b"

DEBUG:swiftclient:RESP STATUS: 204

   Account: AUTH_cd05cd5e6902440c899eaf70ce6a85a6
Containers: 0
   Objects: 0
     Bytes: 0
Content-Type: text/plain; charset=utf-8
X-Timestamp: 1371559166.57340
X-Trans-Id: txbf389d199b7a4974872dc-0051c054fe
X-Put-Timestamp: 1371559166.57340

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.