auth_token middleware should use client
The auth_token middleware should be able to use keystoneclient for all its requests to keystone, but the client is missing some key functions. For v2: fetch the revocation list. For v2 and v3: verify tokens and fetch certificates.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Brant Knudson
- Direction:
- Approved
- Assignee:
- Brant Knudson
- Definition:
- New
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Brant Knudson
- Completed by
- Adam Young
Related branches
Related bugs
Sprints
Whiteboard
This was discused at the keystone mid-cycle and no spec is required.
Gerrit topic: https:/
Addressed by: https:/
Add fetch revocations for v2.0
Addressed by: https:/
Add validate token for v2.0
Addressed by: https:/
Add get certificates for v2.0
Addressed by: https:/
Add fetch revocations for v3
Addressed by: https:/
Add validate token for v3
Addressed by: https:/
Add OS-SIMPLE-CERT support for v3.
Addressed by: https:/
Add sample certificate fixtures
Addressed by: https:/
Tests use keep_blank_values when parse_qs