Enable the use of multiple service tokens (and API)
The service-token in Keystone is used for services to communicate directly with keystone agnostic of the user credentials. Things like listing tenants, etc. Currently keystone supports a single service token, defined in a configuration file as "admin_token" and uses that for authentication and authorization service to service.
We need to support having multiple of those service tokens so that we can have a different service token for each service in the case of many services, and an associated API for CRUD related to the service tokens.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Jesse Andrews
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Joseph Heck
Related branches
Related bugs
Sprints
Whiteboard
i believe this is obsolete based on the current use of service userid/password credentials, or overlaps with the future looking PKI efforts. Jesse - if you disagree, let me know and we can reopen/revisit this.
