Allow a token to be scoped to many projects in the v3 spec

Registered by Joe Savak

In v2 of keystone, tenant is unbounded with respect to token:
https://github.com/openstack/identity-api/blob/master/openstack-identity-api/src/docbkx/common/xsd/token.xsd#L57

In v3 of keystone, a token can only be scoped to 1 project (renamed from tenant in this version):
https://github.com/openstack/identity-api/blob/master/openstack-identity-api/src/markdown/identity-api-v3.md#authenticate-post-tokens

In following the contract for v2 explicitly, we are allowing in our implementation the ability to access multiple default tenants upon authentication. The other method (of going from unscoped to direct-1-tenant-scope works as well).

The change to 1 project per token makes it difficult for us to adopt v3.

I'd like the v3 contract to indicate a list of projects that the token is scoped to. This flexibility in the contract will help us migrate users to v3. This isn't a request to change the reference implementation, just the contract.

Blueprint information

Status:
Complete
Approver:
Joseph Heck
Priority:
Undefined
Drafter:
Joe Savak
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Morgan Fainberg

Related branches

Sprints

Whiteboard

posted for broader discussion: http://markmail.org/message/mwjncy6bbqj3tp3w

this is not really open for discussion at this point. We've got a contract that we have 1 project per token for now. We can reopen this down the road if needed.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.