commit b97f0544e5710df8737ecef795c3b27f475d4c67
author Oleksandr Shyshko <oshyshko@mirantis.com> Fri Sep 07 14:00:18 2018 +0300
committer Oleksandr Shyshko <oshyshko@mirantis.com> Fri Sep 07 14:00:18 2018 +0300
tree c0c94a9bb62791a205d164fbf0e4bb890066063e
parent 0e54b9bacb423ee4e35d82777beaf289131028ad

[REFACTOR] Implement X.509 auth for MySQL and Keystone

Change-Id: I501e26fbc3aca3cba0d27c7541141fb9cb8b9022
Related-PROD: PROD-22748

README.rst

diff --git a/README.rst b/README.rst
index 7603911..0239d03 100644
--- a/README.rst
+++ b/README.rst
@@ -849,19 +849,21 @@
 ---------------------
 By default communication between Keystone and Galera is unsecure.
 
+keystone:
+  server:
+    database:
+      x509:
+        enabled: True
+
 You able to set custom certificates in pillar:
-server:
-  database:
-    x509:
-      enabled: True
 
 keystone:
   server:
     database:
       x509:
-        cacert (certificate content)
-        cert (certificate content)
-        key (certificate content)
+        cacert: (certificate content)
+        cert: (certificate content)
+        key: (certificate content)
 
 You can read more about it here:
     https://docs.openstack.org/security-guide/databases/database-access-control.html