Managing Senstive Data in Murano

Managing Senstive Data in Murano


If you are developing a Murano application that manages sensitive data such as passwords, user data, etc, you may want to ensure this is stored in a secure manner in the Murano backend.

Murano offers two yaql functions to do this, encryptData and decryptData.


Barbican or a similar compatible secret storage backend must be configured to use this feature.


Murano makes use of Castellan to manage encryption using a supported secret storage backend. As of OpenStack Pike, Barbican is the only supported backend, and hence is the one tested by the Murano community.

To configure Murano to use Barbican, place the following configuration into murano-engine.conf:

auth_type = 'keystone_password'
auth_url = <keystone_url>
username = <username>
password = <password>
project_id = <project_id>
user_domain_name = <domain_name>

Similarly, place the following configuration into to configure the murano-dashboard end:

        'auth_url': <keystone_url>/v3',
        'username': <username>,
        'user_domain_name': <domain_name>,
        'password': <password>,
        'project_name': <project_name>,
        'project_domain_name': <domain_name>


encryptData(foo): Call to encrypt string foo in storage. Will return a uuid which is used to retrieve the encrypted value.

decryptData(foo_key): Call to decrypt and retrieve the value represented by foo_key from storage.

There is an example application available in the murano repository.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.