yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #14009
[Bug 1314285] [NEW] /v2.0/tokens/revoked resource not part of the API
Public bug reported:
A recent change (https://review.openstack.org/#/c/78241) checks cached
tokens against the "Revoked Token List". This makes the auth_token.py
middleware do a GET /v2.0/tokens/revoked every time a cached token is
used/validated.
The issue is that I can't find any documentation as to the
/v2.0/tokens/revoked resource. It doesn't seem to be part of the
standard Keystone v2.0 API so I don't know why the client is requiring
Keystone to have it.
This is an issue everywhere the middleware is used. For example, in
Glance, when the new middleware is used I get the following error:
https://gist.github.com/blamarvt/5bff3f4b5de9458479bf
** Affects: keystone
Importance: Undecided
Assignee: Brian Lamar (blamar)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => Brian Lamar (blamar)
** Changed in: keystone
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1314285
Title:
/v2.0/tokens/revoked resource not part of the API
Status in OpenStack Identity (Keystone):
In Progress
Bug description:
A recent change (https://review.openstack.org/#/c/78241) checks cached
tokens against the "Revoked Token List". This makes the auth_token.py
middleware do a GET /v2.0/tokens/revoked every time a cached token is
used/validated.
The issue is that I can't find any documentation as to the
/v2.0/tokens/revoked resource. It doesn't seem to be part of the
standard Keystone v2.0 API so I don't know why the client is requiring
Keystone to have it.
This is an issue everywhere the middleware is used. For example, in
Glance, when the new middleware is used I get the following error:
https://gist.github.com/blamarvt/5bff3f4b5de9458479bf
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1314285/+subscriptions
Follow ups
References