Add rel note and example for TOKEN_DELETE_DISABLED
https://review.openstack.org/#/c/340689 added a new setting to Django OpenStack Auth. This patch documents it and provides an example. Change-Id: Ib684b4c918af0d5ae3770cba702b44e86a3ad3da Closes-Bug: 1609506
This commit is contained in:
parent
d1498101ea
commit
455a1ba62a
@ -1111,6 +1111,16 @@ Example::
|
|||||||
.. note::
|
.. note::
|
||||||
The value is expected to be a tuple formatted as: (<idp_id>, <protocol_id>).
|
The value is expected to be a tuple formatted as: (<idp_id>, <protocol_id>).
|
||||||
|
|
||||||
|
``TOKEN_DELETE_DISABLED``
|
||||||
|
-------------------------
|
||||||
|
|
||||||
|
.. versionadded:: 10.0.0(Newton)
|
||||||
|
|
||||||
|
Default: ``False``
|
||||||
|
|
||||||
|
This setting allows deployers to control whether a token is deleted on log out.
|
||||||
|
This can be helpful when there are often long running processes being run
|
||||||
|
in the Horizon environment.
|
||||||
|
|
||||||
``OPENSTACK_CINDER_FEATURES``
|
``OPENSTACK_CINDER_FEATURES``
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
@ -222,6 +222,11 @@ OPENSTACK_KEYSTONE_BACKEND = {
|
|||||||
# allowing Admin session password retrieval/decryption.
|
# allowing Admin session password retrieval/decryption.
|
||||||
#OPENSTACK_ENABLE_PASSWORD_RETRIEVE = False
|
#OPENSTACK_ENABLE_PASSWORD_RETRIEVE = False
|
||||||
|
|
||||||
|
# This setting allows deployers to control whether a token is deleted on log
|
||||||
|
# out. This can be helpful when there are often long running processes being
|
||||||
|
# run in the Horizon environment.
|
||||||
|
#TOKEN_DELETE_DISABLED = False
|
||||||
|
|
||||||
# The Launch Instance user experience has been significantly enhanced.
|
# The Launch Instance user experience has been significantly enhanced.
|
||||||
# You can choose whether to enable the new launch instance experience,
|
# You can choose whether to enable the new launch instance experience,
|
||||||
# the legacy experience, or both. The legacy experience will be removed
|
# the legacy experience, or both. The legacy experience will be removed
|
||||||
|
@ -0,0 +1,4 @@
|
|||||||
|
---
|
||||||
|
features:
|
||||||
|
- Added the ``TOKEN_DELETE_DISABLED`` setting, so that deployers can
|
||||||
|
customise the revocation of a users token on log out.
|
Loading…
Reference in New Issue
Block a user