Pluggable token formats
keystone.conf's token_format currently has two options, either 'UUID' or 'PKI'. These two options represent slightly different code paths, each with their own token generation and validation logic.
Both should be made pluggable, and the existing UUID and PKI code paths should be extracted into plugins.
token_generator = keystone.
token_validator = keystone.
token_generator = keystone.
token_validator = keystone.
Backwards compatibility should be maintained for overriding token_format such that if 'UUID' is specified, then the default UUID token generator & validator callables should be used, etc.
Additionally, the PKI token_validator should consume keystoneclient.
See related Havana summit etherpad: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Dolph Mathews
- Priority:
- Medium
- Drafter:
- Dolph Mathews
- Direction:
- Approved
- Assignee:
- Guang Yee
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Thierry Carrez
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
pluggable token management
Gerrit topic: https:/
Addressed by: https:/
Pluggable Token Provider (Part 2)
Addressed by: https:/
Pluggable Token Provider (Part 2)
