keystone/keystone/application_credential
Lance Bragstad afca5cc43b Populate application credential data in token
Without this patch, the token formatter does not have enough data to
construct a token created with an application credential. This means
that if the token cache is disabled or expired, when keystone goes to
create the token it will not find any application credential information
and will not recreate the application_credential_restricted parameter in
the token data. This patch creates a new Payload class for application
credentials so that the application credential ID is properly persisted
in the msgpack'd payload. It also adds more data to the token data
object so that the application credential ID and name as well as its
restricted status is available when the token is queried.

Co-authored-by: Lance Bragstad <lbragstad@gmail.com>

Change-Id: I322a40404d8287748fe8c3a8d6dc1256d935d84a
Closes-bug: #1750415
(cherry picked from commit 796198f196)
2018-02-20 08:47:02 +01:00
..
backends Update the base class for application credential 2018-02-03 23:04:03 +00:00
__init__.py Add Application Credentials controller 2018-01-27 11:55:05 +01:00
controllers.py Populate application credential data in token 2018-02-20 08:47:02 +01:00
core.py Add cache invalidation when delete application credential 2018-02-05 14:09:07 +08:00
routers.py Add Application Credentials controller 2018-01-27 11:55:05 +01:00
schema.py Add Application Credentials controller 2018-01-27 11:55:05 +01:00