auth_token Middleware should be able to use Keystone Client

[Jamie Lennox]

Auth token middleware has it's own logic for verifying that a token is valid. This functionality should be generally available as part of keystoneclient and then auth_token middleware should be a consumer of keystone client.

[Jamie Lennox (jamielennox)]

So this will require converting the middleware over to using requests which will mess with a lot of testing. There is a patch i'm trying to get through that will at least handle the requests part of it here: https://review.openstack.org/#/c/34161/ which includes changing over the tests.

It is currently failing because it uses a new testing library which i'm waiting/hoping to be approved: https://review.openstack.org/#/c/34161/

[Jamie Lennox (jamielennox)]

Hi Sayanarayana, just want to check if you're actively working on this? I'm seeing that it might be necessary to add some connection information to keystoneclient config that will also be used here and it will probably turn out nicer if this is done first.

[Dolph Mathews (dolph)]

FWIW, I'm super excited to see this happen.

[Jamie Lennox (jamielennox)]

Confirmed via email that this isn't being worked on yet.

[Jamie Lennox (jamielennox)]

Tracked by blueprint: https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-auth-token

[Dolph Mathews (dolph)]

Unassigning due to inactivity.

[Morgan Fainberg (mdrnstm)]

keystonemiddleware uses ksa and wont be updated for PKI as PKI tokens are deprecated.