Mobile

+916350664837

Secure Runtime Properties in Mulesoft

Application properties are variables that act as placeholders in your Mule application and are set at runtime.

When you deploy an application or update an existing application in Runtime Manager, the Mule runtime engine supplies the values for the property variables using the information you configure in the Properties tab.

For example, you can configure an HTTP request with Basic Authorization in which the username is set to ${username} and the password is set to ${password}. In Runtime Manager, you can set these two properties as application properties.

For sensitive information, you can flag these properties as hidden so that, after they are entered and saved in Runtime Manager, their values are neither visible in the console nor passed between the console and the CloudHub server.

Application properties are variables that act as placeholders in your Mule application and are set at runtime.

When you deploy an application or update an existing application in Runtime Manager, Mule runtime engine supplies the values for the property variables using the information you configure in the Properties tab.

Note: For hybrid deployments, the values remain visible, even after the redeployment.

To create safely hidden application properties:

  1. Add the properties to the appropriate file.
  2. For Mule 4.0 and later, in the mule-artifact.json file under the secureProperties key, list the property names to safely hide as a comma-separated array:

    “configs”: [ “testprops-app.xml” ],  “secureProperties”: [“password”, “username”]
    }
  3. Secure Properties Array shows two secure properties.
  4. Deploy the Mule application to CloudHub.
  5. In the Applications page, click the application name and then click Settings.
  6. In the Properties tab, click List and then enter your application properties.
  7. Click Apply Changes.
  8. Redeploy or restart the app.
  9. After redeploying your app, navigate to the Properties tab.
  10. The values for properties that you marked as safely hidden are now no longer visible to you or any other user.

After the values are committed and the application is uploaded, the safely hidden properties are not displayed on the console or sent and received between the console and the CloudHub server.

After you set the property, you can’t retrieve it; however, you can overwrite the property with a new value. To update a value, enter a new value into the field.

After an application is deployed with safely hidden application properties, CloudHub maintains the security flag for those properties.

 Even if you edit your application file to remove the secureProperties definitions from your mule-artifact.json file and then upload that edited application file to CloudHub, CloudHub maintains the invisibility of the properties previously flagged as safely hidden.

Read More … https://www.linkedin.com/feed/update/urn:li:activity:6807368337945870336

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post

Mulesoft ELKMulesoft ELK

Introduction Use the Elastic Stack (ELK stack) to analyze the business data and API analytics. You can use Logstash for Filebeat to process Anypoint Platform log files, insert them into

Logging in Mule 4Logging in Mule 4

Introduction – Audit Logs Business Group Aware logging to identify access violation. Different user’s activity such as type of action performed for application over an environment is captured here. Payload