Thanks Dolph, obviously my delivery could use some work... The code excerpts were taken before I realised the auth_token issue didn't affect master.
Regarding the breaking API change, note that the SQL backend in stable/grizzly has always only stored the md5 checksum in the token id: https://github.com/openstack/keystone/blob/76a94c68d621c893941a817d36f8ddbe9559dbde/keystone/token/backends/sql.py#L64 https://github.com/openstack/keystone/blob/76a94c68d621c893941a817d36f8ddbe9559dbde/keystone/token/backends/sql.py#L161
So in Grizzly just switching backends also changes the content of the revocation list.
Thanks Dolph, obviously my delivery could use some work... The code excerpts were taken before I realised the auth_token issue didn't affect master.
Regarding the breaking API change, note that the SQL backend in stable/grizzly has always only stored the md5 checksum in the token id: /github. com/openstack/ keystone/ blob/76a94c68d6 21c893941a817d3 6f8ddbe9559dbde /keystone/ token/backends/ sql.py# L64 /github. com/openstack/ keystone/ blob/76a94c68d6 21c893941a817d3 6f8ddbe9559dbde /keystone/ token/backends/ sql.py# L161
https:/
https:/
So in Grizzly just switching backends also changes the content of the revocation list.