From 0f5e41aff390882c4a83436269d03608115b06cc Mon Sep 17 00:00:00 2001
From: Ellen Batbouta <ellen.batbouta@oracle.com>
Date: Thu, 3 May 2018 14:57:50 -0400
Subject: [PATCH] EncryptData method use internal Barbican endpoint

The yaql function, _encrypt_data, now specifies the
Barbican endpoint type to be internal.  This is
necessary when TLS is enabled.

Depends-on: Ic89519ed3a9c347a9fff245ec231aa575b42f1ac

Change-Id: I6f10cb33185800c21eff54b1e4cb001f154362d3
Closes-Bug: #1768299
---
 muranodashboard/dynamic_ui/yaql_functions.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/muranodashboard/dynamic_ui/yaql_functions.py b/muranodashboard/dynamic_ui/yaql_functions.py
index ca3fb8592..ae38d2d5c 100644
--- a/muranodashboard/dynamic_ui/yaql_functions.py
+++ b/muranodashboard/dynamic_ui/yaql_functions.py
@@ -142,6 +142,8 @@ def _encrypt_data(context, data):
         auth_token=auth.get_token(sess), tenant=auth.get_project_id(sess))
     options.set_defaults(cfg.CONF,
                          auth_endpoint=settings.KEY_MANAGER['auth_url'])
+    options.set_defaults(cfg.CONF,
+                         barbican_endpoint_type='internal')
 
     manager = key_manager.API()
     try: