Secure runtime properties mule4
Download as PPTX, PDF0 likes42 views
This document discusses how to securely configure application properties in Mulesoft. It explains that sensitive information like passwords can be marked as hidden properties so their values are not visible after deployment. To create hidden properties, they should be listed in the mule-artifact.json file under the secureProperties key. When the app is deployed, the hidden property values will not be displayed or sent between the console and server.
![• To create safely hidden application properties:
• Add the properties to the appropriate file:
• 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"]
}
Secure Properties Array shows two secure properties.
Create Safely Hidden Application Properties](https://image.slidesharecdn.com/secureruntimeproperties-mule4-210608062527/85/Secure-runtime-properties-mule4-5-320.jpg)
Secure runtime properties mule4
- 2. Introduction • 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.
- 3. Introduction • For example, you can configure a 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.
- 4. Introduction • 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 even after the redeployment.
- 5. • To create safely hidden application properties: • Add the properties to the appropriate file: • 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"] } Secure Properties Array shows two secure properties. Create Safely Hidden Application Properties
- 6. • Deploy the Mule application to CloudHub. • In the Applications page, click the application name and then click Settings. • In the Properties tab, click List and then enter your application properties: Create Safely Hidden Application Properties
- 7. • Click Apply Changes. • Redeploy or restart the app. • After redeploying your app, navigate to the Properties tab. The values for properties that you marked as safely hidden are now no longer visible to you or any other user. Create Safely Hidden Application Properties
- 8. Create Safely Hidden Application Properties
- 9. • 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. Create Safely Hidden Application Properties
- 10. • 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. Create Safely Hidden Application Properties