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.
Reviewed: https:/ /review. openstack. org/545971 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=796198f1967 0e3eb899ca3b1db 5d2a21a4127a30
Committed: https:/
Submitter: Zuul
Branch: master
commit 796198f19670e3e b899ca3b1db5d2a 21a4127a30
Author: Lance Bragstad <email address hidden>
Date: Mon Feb 19 18:23:25 2018 +0000
Populate application credential data in token
Without this patch, the token formatter does not have enough data to credential_ restricted parameter in
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_
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 <email address hidden>
Change-Id: I322a40404d8287 748fe8c3a8d6dc1 256d935d84a
Closes-bug: #1750415