---
schema_version: "1"
id: 2a8779bc01d6853223d8b8e889678d3637682422ee5e7e11a82197e10184fb4c
title: Protecting Mule App Property Values Using RTFCTL
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/2.6/manage-secure-properties.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/2.6/manage-secure-properties
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 861de84da22c9211ace2b69c39488113b15cad0d4a59fc680ec8f722304b9bf4
description: MuleSoft Documentation Site
release: "2.6"
latest: false
---
---
product: Runtime Fabric
version: 2.6
---

# Protecting Mule App Property Values Using RTFCTL

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

Secure application properties are added in the Runtime Fabric cluster locally, stored securely, and
scoped per environment. These properties are accessible in unencrypted form by Mule applications
deployed in the scoped environment as custom properties.

Runtime Fabric protected properties always take precedence over application-level properties.

> [!NOTE] Using secure properties outside of Runtime Manager is discouraged in favor of those
> managed by Runtime Manager.

## Install rtfctl

The `rtfctl` utility is required to manage protected properties on Runtime Fabric locally. Follow
the steps to [install rtfctl](https://docs.mulesoft.com/runtime-fabric/2.6/install-rtfctl) before continuing with managing secure properties.

## Set Secure Properties

1.  Log into a controller node where `rtfctl` is installed.

2.  Run the following command to set a secure property to the Runtime Fabric under a specific
    environment, substituting the placeholder fields:

    ```copy
    rtfctl apply secure-property --key <key> --value <value> --app-namespace <app_namespace> --namespace <rtf_namespace>
    ```

    - **<key>**: The key for the secure property used in the Mule application to reference the
      value.

    - **<value>**: The value for the secure property to store.

    - **<app\_namespace>**: The Anypoint environment to scope this secure property to. Only
      applications deployed to this environment have access to this secure property.

    - **<rtf\_namespace>**:System namespace scope, defaults to `rtf`.

## View Secure Properties

1.  Log into a controller node where `rtfctl` is installed.

2.  Run the following command to view the secure properties applied to the Runtime Fabric under a
    specific environment, substituting the placeholder fields:

    ```copy
    ./rtfctl get secure-properties -n <environment_id>
    ```

    - **<environment\_id>**: The Anypoint environment ID to list the secure properties under.

## Access Secure Properties

You can access secure properties from inside your Mule application using `${my.property.name}`.

## Remove Secure Properties

1.  Log into a controller node where `rtfctl` is installed.

2.  Run the following command to remove a secure property from the Runtime Fabric in a specific
    namespace:

    ```copy
    ./rtfctl delete secure-property <my_key> --app-namespace <namespace>
    ```

    - **<my\_key>**: The key used in the Mule application to reference the secure property.

    - **<namespace>**: The namespace in which the secure property applies.

## Restore RTFCTL Managed Secure Properties

`rtfctl` managed secure properties are directly configured in the cluster and are neither sent nor
stored in the control plane.

Due to this behavior, these secure properties are not included in the backup and restore process, so
they need to be reapplied after restoration.

For details, refer to [Backing Up and Restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/2.6/manage-backup-restore).

## See Also

- [Install rtfctl](https://docs.mulesoft.com/runtime-fabric/2.6/install-rtfctl)

- [Manage Proxies Used by Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/2.6/manage-proxy-self)