Allow any auth mechanism
Middleware is currently hardcoded to allow only username and password authentication against the v2 api.
Keystoneclient provides a mechanism to load any plugin from a config file. We should utilize this to allow arbitrary auth plugins and different auth versions
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Jamie Lennox
- Direction:
- Approved
- Assignee:
- Jamie Lennox
- Definition:
- Approved
- Series goal:
- Accepted for 1.x.x
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Morgan Fainberg
- Completed by
- Jamie Lennox
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Convert authentication into a plugin
Gerrit topic: https:/
Addressed by: https:/
Revert "Support service user and project in non-default domain"
Addressed by: https:/
Allow loading other auth methods in auth_token
Addressed by: https:/
Use connection retrying from keystoneclient
Addressed by: https:/
Add versions to requests
Addressed by: https:/
Use an adapter in IdentityServer
Addressed by: https:/
Use Discovery fixtures for auth token tests
Addressed by: https:/
Split identity server into v2 and v3
Addressed by: https:/
Additional discovery changes
Addressed by: https:/
Use real discovery object in auth_token middleware.
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
