keystone/keystone/token
Morgan Fainberg 37f59f4b0b Update AuthContextMiddleware to not use token_api
AuthContextMiddleware and the fall-through in the controller base
_build_policy_check_credentials now utilizes the KeystoneToken
model and uses token_provider_api instead of token_api.

In support of this change, the token auth plugin, the auth_context
builder, token bind check, and token controller have all been updated
to utilize the KeystoneToken model. Support for the federation data
has been added to the KeystoneToken model so that it can be used
in the auth context and associated code.

Associated tests that passed a raw token_ref to methods that now
expect the KeystoneToken model have been updated. This includes an
update to the revocation model to guard against users without domain
data (the federated user case).

Change-Id: I81da15137a0ab3778d835c8de1ec8ed9e5b301f6
bp: non-persistent-tokens
2014-08-25 21:11:11 -07:00
..
backends Move token persistence classes to token.persistence module 2014-07-24 16:03:50 -07:00
persistence Use functions in oslo.utils 2014-08-09 12:36:09 +00:00
providers Add audit ids to tokens 2014-08-19 23:49:22 +00:00
__init__.py Move token persistence classes to token.persistence module 2014-07-24 16:03:50 -07:00
controllers.py Update AuthContextMiddleware to not use token_api 2014-08-25 21:11:11 -07:00
core.py Move token persistence classes to token.persistence module 2014-07-24 16:03:50 -07:00
provider.py Revoke by Audit Id / Audit Id Chain instead of expires 2014-08-26 04:02:26 +00:00
routers.py HEAD responses should return same status as GET 2014-07-08 22:37:44 -07:00