Client API for revocation events
Revocation events put a few demands on the client. The first is the ability to fetch the rvocation list and check that a given token is/is not revoked based on the list. The second is auth_token middleware changes to (optionally) use the revocation events.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Adam Young
- Direction:
- Needs approval
- Assignee:
- Adam Young
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Dolph Mathews
- Completed by
- Adam Young
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Revocation event API
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add trust users to AccessInfo and fixture
Addressed by: https:/
Add role ids to the AccessInfo
Addressed by: https:/
Add issued handlers to auth_ref and fixtures
Addressed by: https:/
Add OAuth data to AccessInfo
Addressed by: https:/
Direct move of the model code from keystone server
Gerrit topic: https:/
Gerrit topic: https:/
