Use a shared session key among Horizon nodes
This change adds a configuration setting for the Horizon session key. If present, this key is set into all Horizon nodes, so that they can share sessions. Change-Id: I94f46f3adb8fa26965959d5e8c6473eff1b4591c Closes-bug: 1403611
This commit is contained in:
parent
ec3a14f235
commit
b5fbb9a673
@ -83,7 +83,7 @@ heat_cfn_service_password:
|
||||
|
||||
## Horizon Options
|
||||
horizon_container_mysql_password:
|
||||
|
||||
horizon_secret_key:
|
||||
|
||||
## MaaS Options
|
||||
# Set maas_auth_method to 'token' to use maas_auth_token/maas_api_url
|
||||
|
@ -94,8 +94,12 @@ LOCAL_PATH = os.path.dirname(os.path.abspath(__file__))
|
||||
# behind a load-balancer). Either you have to make sure that a session gets all
|
||||
# requests routed to the same dashboard instance or you set the same SECRET_KEY
|
||||
# for all of them.
|
||||
{% if horizon_secret_key %}
|
||||
SECRET_KEY = "{{ horizon_secret_key }}"
|
||||
{% else %}
|
||||
from horizon.utils import secret_key
|
||||
SECRET_KEY = secret_key.generate_or_read_from_file('/var/lib/horizon/.secret_key_store')
|
||||
{% endif %}
|
||||
|
||||
# We recommend you use memcached for development; otherwise after every reload
|
||||
# of the django development server, you will have to login again. To use
|
||||
|
Loading…
x
Reference in New Issue
Block a user