Move federated auth plugins to separate repositories
keystoneclient should not have federated auth plugins implemented in its namespace. This blueprint aims to add a interface-like class used for federated auth plugins implementation as well as move any federated auth plugins to corresponding repositories.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Marek Denis
- Direction:
- Needs approval
- Assignee:
- Marek Denis
- Definition:
- Superseded
- Series goal:
- Accepted for liberty
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
(stevemar 2016-07-31): This was resolved by moving all keystone auth plugins to keystoneauth, and using "extras" to make them optionally installable.
Gerrit topic: https:/
Addressed by: https:/
Refactor federation plugins.
Addressed by: https:/
Standardize federated auth token scoping
Addressed by: https:/
Rename v3/federated.py to federation.py
