OpenStack Object Storage (swift)

keystoneauth fail to accept tenant_name

Bug #1077611 reported by David Hadas on 2012-11-11

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Object Storage (swift)	Invalid	Undecided	David Hadas

Bug Description

URI such as /v1/AUTH_mytenant/mycontainer/myobject is rejected by keystoneauth although a legal tenant is indicated

Instead, current implementation support only the use of tenant_id in the URI
Such as /v1/AUTH_584c077e94e44cdab4a70926c5e8c0c0/mycontainer/myobject

Suggested fix - allow both tenant_id and tenant_name to be used.

David Hadas (david-hadas) on 2012-11-11

Changed in swift:
assignee:	nobody → David Hadas (david-hadas)

Revision history for this message

Kun Huang (academicgareth) wrote on 2013-02-24:

How to implement that "both"? When user send credentials to keystone, he will be response with endpoints of each service. How to implement "both" here? For more, proxy-server will get AUTH_mytenant or AUTH_584c077e94e44cdab4a70926c5e8c0c0 as account. How does server choose? To have a try with sending another request is not a good idea in my mind.

Kun Huang (academicgareth) on 2013-03-29

Changed in swift:
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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