---
schema_version: "1"
id: e76d79daee0c075dda75943b64eed2558da60111fbb3cc211291d6815329d76d
title: Protecting Mule App Property Values in Runtime Fabric
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/2.6/protect-app-properties.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/2.6/protect-app-properties
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 2ba02f2519cd23e41adb12c291813b84b07a77e797714d2347007770d0a43a57
description: MuleSoft Documentation Site
release: "2.6"
latest: false
---
---
product: Runtime Fabric
version: 2.6
---

# Protecting Mule App Property Values in Runtime Fabric

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Runtime Fabric enables you to protect application property values by displaying the
property name, but not its value, in Anypoint Runtime Manager.

Additionally, a protected value is not viewable or retrievable by any user. Runtime Fabric resolves
the property internally at runtime. These protected application values are encrypted and stored in
the Anypoint Security secrets manager, which, in turn, is encrypted per user organization.

Protected property values are separate from the encrypted Mule application properties that are
stored in secure configuration files. See
[Secure Configuration Properties](https://docs.mulesoft.com/mule-runtime/latest/secure-configuration-properties).

> [!NOTE] Runtime Manager does not support adding protected properties for API proxies or gateways.
> Instead, use API Manager.

> [!NOTE] Protecting API Gateway client ID and secret ID is currently supported in Runtime Fabric,
> either via API or the Anypoint Runtime Manager UI.

## Protect Property Values in Runtime Manager

Set protected properties via the table view for granular control over each property and value.

Although you may attempt to protect a single property more than once, Runtime Manager issues a
warning and only the final instance of that property is protected.

1.  From Anypoint Platform, select Runtime Manager.

2.  From the left menu, click **Applications**.

3.  Click the application name.

4.  On the **Settings** page, click the **Properties** tab.

5.  Depending on how many properties you want to protect at once, take one of the following actions:

    - To protect properties one at a time, click **Table view**.

    - To protect multiple properties, use **Text view** to add the key-value pairs and then switch
      to **Table view**, and continue to Step 8.

6.  In the **New Key** field, add a property to protect.

7.  In the **New Value** field, add a value.

    ![Adding properties in table view](/mulesoft/current/en-us/runtime-fabric/2.6/_images/rtf-add-protected-properties.png)

8.  Click **Protect** > **Protect value** to confirm.

9.  Choose from one of the following:

    - If this application has already been deployed, click **Apply changes**.

    - If you’re ready to deploy the application, click **Deploy Application**.

In the **Properties** tab, the values for properties that you just protected are now no longer
visible to you or any other user.

In the following example, the value for `dbPassword` is protected but those for `dbUsername` and
`environment` are not:

![The value for dbpassword is shown as protected](/mulesoft/current/en-us/runtime-fabric/2.6/_images/rtf-view-protected-properties.png)

After you commit the values and deploy the application, the protected property values don’t appear
in the console and aren’t sent and received between the console and Runtime Manager.

## Replace a Protected Property Value

After you protect a property value, you can’t retrieve it. However, you can replace the protected
property value with a new protected value:

1.  In the Table view, click the icon next to the protected value that you want to replace.

2.  Click the menu icon next to the value and then click **Replace protected value**.

3.  Enter a new value in the field

4.  Click **Apply** > **Apply changes.**