From 846b4fe0b82f861c3f6c637cdc5d7d9f052e4338 Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Tue, 8 Dec 2015 16:08:22 +0200 Subject: Enable X-Forwarded-Proto header for keystone_public One of the ways to make use of TLS in keystone is through the usage of the X-Fowarded-Proto header, which will be forwarded with the request by the loadbalancer, and it will tell keystone what protocol was used to access it. This also requires configuration from the keystone side. Change-Id: I9b899ba95e28b7dfae0c1ed84ca8431054673925 --- manifests/loadbalancer.pp | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'manifests/loadbalancer.pp') diff --git a/manifests/loadbalancer.pp b/manifests/loadbalancer.pp index e34b01e..c4a317b 100644 --- a/manifests/loadbalancer.pp +++ b/manifests/loadbalancer.pp @@ -685,6 +685,10 @@ class tripleo::loadbalancer ( haproxy::listen { 'keystone_public': bind => $keystone_public_bind_opts, collect_exported => false, + mode => 'http', # Needed for http-request option + options => { + 'http-request' => ['set-header X-Forwarded-Proto https if { ssl_fc }'], + }, } haproxy::balancermember { 'keystone_public': listening_service => 'keystone_public', -- cgit 1.2.3-korg