e8d0f0db5f
Ther X-Forward-Proto header should be added on the external loadbalancer only, otherwise admin, internal endpoint requests to keystone may suddenly flip to HTTPS while HTTP is configured in default. This also affects request to local keystone API calls for monitoring etc. Closes-Bug: #2068039 Change-Id: I4cfef16841f95328d4ae7e4666f5a8fac053440b
9 lines
352 B
YAML
9 lines
352 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The variable ``keystone_external_ssl`` was deprecated and is no longer used.
|
|
You still can control if communication between HAProxy and Keystone should
|
|
be covered with TLS through ``keystone_backend_ssl`` or
|
|
``haproxy_ssl``/``haproxy_ssl_all_vips`` for communication between clients
|
|
and HAProxy on frontend.
|