Allow scoping to a domain, as well as a project
The v3 API has introduced the concept of Domains, being the container that holds users and projects. For many cloud providers, the domain will be the object that really maps to a hosted customer, within which that customer will CRUD their users and projects. To facilitate this, the customer will want to create users that have "roles" that are domain wide (e.g. on-board new users, maintain a set of standard images for all projects etc.). To aid this, we should support the scoping of a token to a Domain (either at authentication or subsequent /tokens call)
Blueprint information
- Status:
- Complete
- Approver:
- Joseph Heck
- Priority:
- Medium
- Drafter:
- Henry Nash
- Direction:
- Approved
- Assignee:
- Henry Nash
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
2013.1
- Started by
- Henry Nash
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Keystone backend preparation for domain-scoping
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
domain-scoping
Work Items
Work items:
Plumbing for domain_id in all relevant entities: DONE
Integrate with v3 auth (https:/
