PKI-signed token hash saved as token ID for SQL backend only
Bug #1073272 reported by
Gabriel Hurley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Russell Cloran | ||
| Folsom |
Fix Released
|
Medium
|
Adam Young | ||
Bug Description
In the SQL backend, the id of the token is stored as the MD5 hash of the full PKI-signed token, whereas in the KVS backend, keys off the full token.
To enable consumers to reliably use the MD5 hash for API calls, etc. we need to have the KVS backend behave the same way as the SQL backend.
| Changed in keystone: | |
| assignee: | nobody → Russell Cloran (russell) |
| status: | New → In Progress |
Revision history for this message
| Adam Young (ayoung) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (master) | #3 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| milestone: | none → grizzly-1 |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (stable/folsom) | #4 |
| Changed in keystone: | |
| milestone: | grizzly-1 → 2013.1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (stable/folsom) | #5 |
To post a comment you must log in.
Please make sure it works for both KVS and Memcached backends.