---
schema_version: "1"
id: e8e31c54b27dde9236269dc1f60952d90ac1e863bdf1fcca9c1e3dcfc804ba61
title: Secrets Manager Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/anypoint-security/secrets-manager-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/anypoint-security/secrets-manager-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8e729ea89419e3c12179e48cb3e17ed0ab836d7656085e97c879a3ceef211717
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Secrets Manager Release Notes

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

## October 2, 2025

Secrets Manager now supports TLS 1.3 for TLS Contexts. When creating or modifying a TLS Context for
Mule, TLS 1.3 from the list of supported protocols. This enhancement enables your Mule applications
to leverage the latest security standards, ensuring more secure and performant connections with
external services.

## February 20, 2021

Starting with this release, Secrets Manager no longer uses the lock feature when creating or
modifying a secrets group. In previous versions of Secrets Manager, changes made to a secrets group
were not applied until you clicked **Finish** to commit the changes. After this update, changes to a
secret group, such as creating a key store or TLS context, are applied as soon as they are created
or saved. The **Finish** and **Cancel Edit** buttons are no longer applicable.

## March 30, 2020

When creating a TLS context using Secrets Manager, the expiration date incorrectly defaults to one
year for keystore expirations that are shorter than one year. (SE-15141)

Workaround: Manually enter the correct expiration date in the **Expiration Date** field when
creating or editing a TLS context.

## November 9, 2019

This release has the following known issue:

In the Secret Groups left navigation, **CRL Distributor Config** appears, but it is not yet
supported, and you can’t add a Certificate List Distributor (CRL) configuration to your Secret
Group.

## January 12, 2019

This Secrets Manager release has the following fixed issue:

### Users Unable to Perform Actions in Secrets Manager

When users of business groups accessed the Secrets Manager user interface, the
`do not have permission` error occurred when trying to perform actions in Secrets Manager. This
happened even though the root organization (or a parent of a business group) had the **API Manager
Environments** entitlement.

FIX: If the root organization has the **API Manager Environments** entitlement, users of the child
business groups are now able to access Secrets Manager functionality.

For more information about Secrets Manager, see
[Secret Groups](https://docs.mulesoft.com/anypoint-security/asm-secret-group-concept)

## See Also

- [Known Issues](https://help.salesforce.com/s/issues)