---
schema_version: "1"
id: aa635971c7502a24e8aa902e384ecd07eecd26c6ae0b88968df86f1b8829bf2a
title: Add a TLS Context to Mule
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-security/secret-group-add-tls-context.md
canonical_url: https://docs.mulesoft.com/anypoint-security/secret-group-add-tls-context
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 71e82971df66dbac3e0eb4543547970c0889a23a4702f5d44927e170f377a5a6
description: MuleSoft Documentation Site
latest: true
---
---
product: Security
version: master
---

# Add a TLS Context to Mule

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

After you create a secret group, you can add a Transport Layer Security (TLS) context to encrypt
inbound traffic to Mule 4 proxies. When you add the TLS context, you can select the ciphers to use
with the TLS context.

You can use the TLS context you store in the secrets manager when you configure an HTTPS API proxy.

## Add TLS Context

Adding a TLS context to your secret group involves supplying a name, target, security information,
version, keystore and, optionally, truststore.

1.  In the **Secret Groups** list view, select the secret group to which to add a TLS context.

2.  Select **TLS Context** in the menu on the left, and click **Add TLS Context**.

3.  In the Create TLS Context screen, add the required information:

    - **Name**  
      Enter a name for your TLS context.

    - **Target**  
      Select **Mule** to use the TLS context as the SSL validation for Mule 4-based API proxies.
      Uses the TLS context as the SSL validation for Mule 4-based API proxies.

    - **TLS Version**  
      By default, TLS 1.3 is selected. You can select TLS 1.2 to support both versions.

    - **Keystore**  
      From the drop-down list, select the keystore associated with the TLS context.

    - **Truststore**  
      Optionally, select a truststore associated with the TLS context if you are using a truststore
      to store certificates trusted by the client.  
      If the Target value for the TLS context is **Mule**, you can select **Insecure** if you don’t
      want certificate validation enforced.

    - **Expiration Date**  
      Optionally, select the expiration date for the TLS context. The information is considered as
      metadata of the TLS context. The expiry date of the certificates in the associated keystore or
      truststore doesn’t change.

4.  Optionally, [select ciphers](https://docs.mulesoft.com/anypoint-security/cipher-suites) for the TLS context.

5.  Click **Save**.

## See Also

- [Create a Secret Group](https://docs.mulesoft.com/anypoint-security/asm-secret-group-creation-task)