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	Add expired_at_int column to trusts	2018-01-04 22:28:44 +01:00
__init__.py	Remove exposure of routers at package level	2015-12-03 15:06:56 -03:00
controllers.py	Populate application credential data in token	2018-02-20 08:47:02 +01:00
core.py	Use keystone.common.provider_api for trust APIs	2018-01-08 14:35:49 +00:00
routers.py	Ensure the trust API supports HEAD requests	2017-06-21 15:04:03 +00:00
schema.py	Fix role schema in trust object	2017-11-28 15:21:45 +01:00