Enforce multi-tenancy using the Keystone domain/project the user authenticated to
In order to support multiple tenants on the same MagnetoDB deployment, we need to enforce isolation to the domain/project that the user authenticated to. As examples...
- User authenticates to project A, lists tables, only sees the tables created within project A.
- User authenticates to project A, tries to access a table in project B, and gets a failure response.
- User 1 auths to project A and creates a table named "foo". User 2 auths to project B and creates a table named "foo". These are maintained as two separate tables.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Keith Newstadt
- Direction:
- Needs approval
- Assignee:
- Alexander Chudnovets
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Alexander Chudnovets
- Completed by
- Alexander Chudnovets
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Added keystone v3 support
Work Items
Dependency tree
* Blueprints in grey have been implemented.
