A Key Distribution Server that release tickets to be used for RPC Messaging Security
MessageSecurity requires a central repository to register service identies, manage grou pof sevices and store shared keys,a s well as provide a ticketing system to allow secure communication between parties (signing and optionally encryption services).
The Key Distribution Server manages the ticketing system and stores shared keys between the Server itself and the registered servies. It may also store temporary group keys.
This server is necessary for the implementation of https:/
After https:/
Blueprint information
- Status:
- Complete
- Approver:
- Adam Young
- Priority:
- Undefined
- Drafter:
- Simo Sorce
- Direction:
- Needs approval
- Assignee:
- Jamie Lennox
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Needs Code Review
- Milestone target:
- None
- Started by
- Thierry Carrez
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
This is not a Keystone project/spec. Marking as obsolete.
API spec review: https:/
Gerrit topic: https:/
Addressed by: https:/
Add crypto dependency
Addressed by: https:/
Sync-up crypto from oslo-incubator
Addressed by: https:/
Initial KDS service
Addressed by: https:/
Add group key support
Gerrit topic: https:/
Addressed by: https:/
Initial KDS service
Addressed by: https:/
Add support to delete keys and groups
Addressed by: https:/
Initial KDS service
Addressed by: https:/
Sync From OSLO
Addressed by: https:/
Introduce basic Pecan/WSME framework for KDS
Addressed by: https:/
Introduce database functionality into KDS
Addressed by: https:/
Add cryptographic key storage
Addressed by: https:/
Add ticket handling to KDS
Addressed by: https:/
Add group support to KDS
Addressed by: https:/
Update from Global Requirements
Addressed by: https:/
Move KDS paths file
Addressed by: https:/
Add version routes to KDS
Work Items
Dependency tree
* Blueprints in grey have been implemented.