Add is_domain to the token
When a project token to be issued on a project acting as a domain, we should include is_domain=True in the token. By doing this, you can write policy rules that use project tokens to manage access to domain related entities (like users). We should still keep domain tokens for now, but this would be a step towards removing them.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Henry Nash
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add is_domain to tokens for projects acting as a domain
Addressed by: https:/
API changes for Reseller
Gerrit topic: https:/
Addressed by: https:/
Change project name constraint
Addressed by: https:/
Add is_domain in token response
Addressed by: https:/
Bye Bye Domain Table
Addressed by: https:/
Remove domain table references
Addressed by: https:/
Honor domain operations in project table
Addressed by: https:/
WIP: Change policy to comply with is_domain in token
Addressed by: https:/
Add is_domain field in Project Table
Addressed by: https:/
Creating tests for projects acting as domains
Addressed by: https:/
Limit subtree and parents queries
Addressed by: https:/
Replicate domain info in projects table
Addressed by: https:/
Add is_domain parameter to get_project_by_name
