What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How you hide an application property in CloudHub depends on the platform generation. In CloudHub 1.0, declare the property name in mule-artifact.json under secureProperties, then set its value in Runtime Manager. In CloudHub 2.0, enable protection for the value directly in Runtime Manager’s Properties tab. A CloudHub 1.0 secureProperties declaration does not mask values on CloudHub 2.0.
Identify your CloudHub generation first
Use the workflow that matches the platform hosting the application. The controls are not interchangeable:
| Platform | Where protection is configured | How the protected value is managed |
|---|---|---|
| CloudHub 1.0 | secureProperties in mule-artifact.json, then Runtime Manager |
Runtime Manager stores the hidden application property; the value is not displayed after saving |
| CloudHub 2.0 | Runtime Manager Properties tab | Enable protection for each value; MuleSoft stores protected values in Anypoint Security secrets manager |
Hide properties on CloudHub 1.0
1. Declare the property names
For Mule 4.0 and later applications, add every property name that must be hidden to the secureProperties array in mule-artifact.json. The declaration identifies names, not their secret values.
{
"secureProperties": [
"db.password",
"api.client.secret"
]
}2. Deploy and enter the values in Runtime Manager
- Deploy the application to CloudHub 1.0.
- In Runtime Manager, open the application’s Settings.
- Open the Properties tab.
- Enter values for the names declared in
secureProperties. - Apply the changes.
- Restart or redeploy the application so the updated configuration is used.
The property names remain visible for configuration purposes, but their values are hidden. CloudHub keeps a property’s hidden status after it has been flagged, even if a later application archive removes that name from secureProperties.
#1 Best Overall
3. Rotate a value by replacement
A saved hidden value cannot be read back. To rotate it, enter a new value for the same property and apply the change. This is replacement, not retrieval.
4. Set values again in another sandbox
When an application is moved between sandboxes, property names are copied but safely hidden values are left blank. Supply the destination environment’s values in its Runtime Manager Properties tab.
Protect properties on CloudHub 2.0
Use Runtime Manager property protection
- Open the CloudHub 2.0 application in Runtime Manager.
- Open the Properties tab.
- Add or edit the property.
- Enable the property’s protection option before saving.
- Save the configuration and deploy or restart as required by your change.
Protected values are encrypted, are not viewable or retrievable by users, and are resolved internally when the application runs. Overwrite a value by entering a replacement value; plan rotation without relying on a read-back operation.
Do not rely on the CloudHub 1.0 declaration
CloudHub 2.0 does not use a CloudHub 1.0 secureProperties declaration to configure masking. Set protection in Runtime Manager for each CloudHub 2.0 property that needs it.
Understand precedence
For a property with the same name, a Runtime Manager value overrides the value bundled in the application archive. CloudHub 2.0 documentation lists a maximum of 300 properties, with keys and values limited to 1,024 characters; verify these limits in current deployment documentation if your application approaches them.
Keep platform hiding separate from encrypted configuration files
These are different mechanisms:
- Platform-side hiding: protects an operator-entered Runtime Manager property. Use this when the objective is to keep a CloudHub setting from being displayed or retrieved.
- Secure configuration properties: bundles encrypted property data in the application archive. The application still needs the decryption key at deployment or runtime, and that key should not be packaged in the archive.
On CloudHub, the decryption key itself can be supplied as a safely hidden application property. The application decrypts the configuration values at runtime, but this does not turn archive contents into Runtime Manager-protected properties.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Prevent deployment automation from wiping protected values
CloudHub 2.0 deployments made with the Mule Maven Plugin require special care. If the deployment POM includes either a top-level properties or secureProperties element, CloudHub uses the set defined in the POM instead of merging it with the values already configured in Runtime Manager. Existing properties omitted from that set are removed.
Choose the deployment behavior deliberately
- Supply properties from the POM: include the complete intended set on every redeployment, including all protected values that must remain.
- Preserve Runtime Manager values: omit both
propertiesandsecurePropertiesfrom the POM. Existing Runtime Manager values remain in place.
Review the POM before redeploying a CloudHub 2.0 application, especially when a pipeline or release process was created for CloudHub 1.0.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Operational checklist
- Confirm whether the target is CloudHub 1.0 or CloudHub 2.0.
- Use
mule-artifact.jsonsecurePropertiesonly for the CloudHub 1.0 declaration workflow. - Enable protection in Runtime Manager for each CloudHub 2.0 secret value.
- Record the property names, but do not expect to recover saved values.
- Rotate secrets by overwriting them with newly issued values.
- Provide values separately in each sandbox or environment.
- Keep encryption keys for secure configuration files outside the packaged application.
- On CloudHub 2.0, inspect Maven deployment parameters so a redeploy does not remove Runtime Manager properties.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
