From 2e08ffd6d3104b784cbdbe2a8a2f37cb98ff43d3 Mon Sep 17 00:00:00 2001 From: James Kirsch Date: Thu, 7 May 2020 15:49:56 -0700 Subject: Add support for encrypting Barbican API This patch introduces an optional backend encryption for the Barbican API service. When used in conjunction with enabling TLS for service API endpoints, network communcation will be encrypted end to end, from client through HAProxy to the Barbican service. Change-Id: I62a43b36ebe4a03230bf944980b45e4b6938871b Partially-Implements: blueprint add-ssl-internal-network --- releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'releasenotes') diff --git a/releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml b/releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml index bfe710a8b..72bb28801 100644 --- a/releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml +++ b/releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml @@ -2,7 +2,7 @@ features: - | Added configuration options to enable backend TLS encryption from HAProxy - to the Keystone, Glance, Heat, Placement, Horizon, and Cinder services. - When used in conjunction with enabling TLS for service API endpoints, - network communcation will be encrypted end to end, from client through - HAProxy to the backend service. + to the Keystone, Glance, Heat, Placement, Horizon, Barbican, and Cinder + services. When used in conjunction with enabling TLS for service API + endpoints, network communcation will be encrypted end to end, from client + through HAProxy to the backend service. -- cgit v1.2.3