copyright

lastupdated

keywords

subcollection

content-type

years
2020, 2025

2025-01-16

release notes for Secrets Manager, what's new, enhancements, fixes, improvements, Secrets Manager

secrets-manager

release-note

{:codeblock: .codeblock} {:screen: .screen} {:download: .download} {:external: target="_blank" .external} {:faq: data-hd-content-type='faq'} {:gif: data-image-type='gif'} {:important: .important} {:note: .note} {:pre: .pre} {:tip: .tip} {:preview: .preview} {:deprecated: .deprecated} {:beta: .beta} {:term: .term} {:shortdesc: .shortdesc} {:script: data-hd-video='script'} {:support: data-reuse='support'} {:table: .aria-labeledby="caption"} {:troubleshoot: data-hd-content-type='troubleshoot'} {:help: data-hd-content-type='help'} {:tsCauses: .tsCauses} {:tsResolve: .tsResolve} {:tsSymptoms: .tsSymptoms} {:video: .video} {:step: data-tutorial-type='step'} {:tutorial: data-hd-content-type='tutorial'} {:api: .ph data-hd-interface='api'} {:cli: .ph data-hd-interface='cli'} {:ui: .ph data-hd-interface='ui'} {:terraform: .ph data-hd-interface="terraform"} {:curl: .ph data-hd-programlang='curl'} {:java: .ph data-hd-programlang='java'} {:ruby: .ph data-hd-programlang='ruby'} {:c#: .ph data-hd-programlang='c#'} {:objectc: .ph data-hd-programlang='Objective C'} {:python: .ph data-hd-programlang='python'} {:javascript: .ph data-hd-programlang='javascript'} {:php: .ph data-hd-programlang='PHP'} {:swift: .ph data-hd-programlang='swift'} {:curl: .ph data-hd-programlang='curl'} {:dotnet-standard: .ph data-hd-programlang='dotnet-standard'} {:go: .ph data-hd-programlang='go'} {:unity: .ph data-hd-programlang='unity'} {:release-note: data-hd-content-type='release-note'}

Release notes for {{site.data.keyword.secrets-manager_short}}

{: #release-notes}

Use these release notes to learn about the latest changes to {{site.data.keyword.secrets-manager_full}} that are grouped by date. {: shortdesc}

For the latest changes to the APIs, check out the {{site.data.keyword.secrets-manager_short}} API change log.

13 January 2025

{: #secrets-manager-january1325} {: release-note}

Common Name for public_cert secret type is now optional. : {{site.data.keyword.secrets-manager_short}} is now aligned with Let's Encrypt latest changes, where the previous 64 chars restriction on the Common Name field is no longer required. If the Common Name of a certificate is not explicitly specified by the user, Let's encrypt will automatically assign the first alt name that is not longer than 64 chars as the Common Name. If no such alt name is found the certificate will be issued without a Common name.

19 November 2024

{: #secrets-manager-november1924} {: release-note}

New event notifications for secret types : You can now configure Event Notifications to send an alert for all secret types when a secret is created or fails creation. To learn more about the integration, see Enabling event notifications for {{site.data.keyword.secrets-manager_short}}.

7 October 2024

{: #secrets-manager-october724} {: release-note}

Rotation of intermediate CA certificates : A new configuration action_type, private_cert_configuration_action_rotate_intermediate, is now available to enable rotation of an intermediate CA's certificate. Learn more about rotating an intermediate CA.

23 September 2024

{: #secrets-manager-september2324} {: release-note}

Create IAM service authorizations through the IAM credentials secret engine : You can now use IAM service authorization to configure the IAM credentials engine instead of maintaining an API key. In addition, you can now create IAM credentials secrets either from the current {{site.data.keyword.cloud_notm}} account or from a specific other account. Learn more about how to configure and create IAM credentials.

See the expiration date of previous secret versions : You can see the expiration date of the previous version for a rotated secret in the version history side panel.

12 August 2024

{: #secrets-manager-august1224} {: release-note}

Support for HSM in Private Certificates : You can use the Private Certificate engine to generate Root and Intermediate CA certificates with private keys managed by a Hardware Security Module (HSM). This feature is currently available using {{site.data.keyword.hscrypto}} HSM.

Finer granularity in Configurations API : Use the secret_types option to list configuration for a specific engine. Supported values are: iam_credentials, public_cert, and private_cert.

3 June 2024

{: #secrets-manager-june0324} {: release-note}

Service metrics : You can now monitor and gain operational visibility into the performance and health of your {{site.data.keyword.secrets-manager_short}} instance. To learn more, see Monitoring operational metrics.

13 May 2024

{: #secrets-manager-may1324} {: release-note}

Enhanced UI : Users of private-only service instances can now access the full experience of the service UI.

18 March 2024

{: #secrets-manager-march1824} {: release-note}

Key management service : The Settings page now displays the key management service selected for the service instance - provider-managed, or user-provided ({{site.data.keyword.keymanagementserviceshort}} or {{site.data.keyword.hscrypto}}).

11 March 2024

{: #secrets-manager-march1124} {: release-note}

Additional filter options : You can now filter by secret types as well as filter for more than one label.

12 February 2024

{: #secrets-manager-feb1224} {: release-note}

Support for random password generation in User credentials : The User credentials secret type now supports generating a random password on secret creation. In addition you can control the password's length, and whether to include numbers, symbols and upper-case letters. To learn more, see Storing user credentials.

10 January 2024

{: #secrets-manager-jan1024} {: release-note}

New event notifications for secret types : You can now configure Event Notifications to send an alert for all secret types when a secret is rotated or deleted. To learn more about the integration, see Enabling event notifications for {{site.data.keyword.secrets-manager_short}}.

11 December 2023

{: #secrets-manager-dec1123} {: release-note}

Manage service credentials for supported {{site.data.keyword.cloud_notm}} services : You can now use {{site.data.keyword.secrets-manager_short}} to create and manage service credentials for supported services. To learn more, see What is a secret and Create a Service credential.

4 December 2023

{: #secrets-manager-dec0423} {: release-note}

Madrid availability : You can now create a {{site.data.keyword.secrets-manager_short}} service instance in the Madrid (eu-es) region.

For more information, see Regions and endpoints.

6 November 2023

{: #secrets-manager-nov0623} {: release-notes}

Updated {{site.data.keyword.secrets-manager_short}} UI : An updated version of the {{site.data.keyword.secrets-manager_short}} UI is now available and includes the following improvements:

* New flow for adding secrets
* New Secrets Details side panel
* Ability to get a secret engine's configuration value for public_cert, private_cert, and iam_credentials
* Ability to get a secret engine's configuration code snippet for public_cert, private_cert, and iam_credentials
* Ability to get the secret value of the current and previous secret versions
* IAM credentials now display an expiration date in the Secrets table when the reuse apikey is set to true
* Improvements to the IAM Credentials secret engine page:
  * Ability to delete a configuration if all IAM credential secrets are first deleted
  * Look and feel enhancements
  * Visual cue for an invalid configuration that is missing or has a misconfigured API key
* Multi-select up to 5 secrets to download or delete, depending on the secret type

20 September 2023

{: #secrets-manager-sept2023} {: release-note}

Now available: Get a secret by name : Users can now get a secret and its details by specifying the name and type of the secret through the API. This functionality is also available in CLI and SDKs

19 April 2023

{: #secrets-manager-apr1923} {: release-note}

Now available: CLI v2.0.1 : A new version of the {{site.data.keyword.secrets-manager_short}} CLI is now available. In this release, the CLI was updated to address an error that Windows users faced when they attempted to download the plug-in.

17 April 2023

{: #secrets-manager-apr1723} {: release-note}

Now available: API, SDK, CLI, and Terraform v2.0 : A new version of the {{site.data.keyword.secrets-manager_short}} API and SDKs is now available. The following updates are included in this release.

You no longer need to include secret_type in the API URL to identify a secret.
The secret group name must be unique per {{site.data.keyword.secrets-manager_short}} instance.
Resources updates are defined as HTTP patch operations.
The configurations API follows the pattern of the {{site.data.keyword.secrets-manager_short}} API. config_type acts as the API discriminator, similarly to secret_type.
Configurations are modeled as openAPI composites with metadata and data parts, similarly to the {{site.data.keyword.secrets-manager_short}} model. Mappings between IAM roles and configurations API follow the same pattern for the {{site.data.keyword.secrets-manager_short}} API. For example, an IAM viewer can list configurations to view their metadata.
List operations return metadata only for secret, secret version, and config resources.
The action to rotate a secret is now the create a new secret version API: POST/v2/secrets/{id}/versions.
The action to restore secret version is now the create a new secret version API with the restored_from_version body parameter.
The action to delete IAM credentials is now the delete a secret version data API: DELETE /v2/secrets/{id}/versions/{version_id}/secret_data.
Policies API is now embedded into the metadata API in version 2.0.
The actions to list Secrets and get secret metadata return the versions_total field. The version's content is not included.
Current and previous secret versions can be referenced by using the current and previous aliases in version APIs.
The secret lock mode names exclusive and exclusive_delete are replaced by remove_previous and remove_previous_and delete. The modes still perform the same action, only the names changed.
CLI commands to create secret/group/configuration require JSON input instead of param flags.
CLI command names for configurations and locks slightly changed.

For more information, check out the API docs.

Now available: CLI version 2.0 : A new version of the {{site.data.keyword.secrets-manager_short}} CLI is now available. For more information about the updates that are included in version 2.0, check out the CLI change log.

Deprecated: API, SDK, and CLI v1 : As of April 17, 2023, the {{site.data.keyword.secrets-manager_full}} API v1 has been deprecated in favor of v2. If you're still actively working with the {{site.data.keyword.secrets-manager_short}} API v1, please be sure to start your upgrade as soon as possible. On 31 October 2023, support for the {{site.data.keyword.secrets-manager_short}} API v1 will be removed.

3 March 2023

{: #secrets-manager-mar0323}

Now available: Terraform support : {{site.data.keyword.secrets-manager_short}} now supports Terraform on {{site.data.keyword.cloud_notm}}. For more information, see Setting up Terraform for {{site.data.keyword.secrets-manager_short}} and the Terraform registry{: external}.

11 December 2022

{: #secrets-manager-dec1122} {: release-note}

Support for context-based restrictions (CBR) : Manage user and service access to your {{site.data.keyword.secrets-manager_short}} resources by using context-based restrictions, based on defined criteria. For more information, see Managing access with context-based restrictions.

As part of the support for CBR, the private service inner IPs were modified. The hostnames were not modified. If needed, you can use DNS lookup to find the exact IPs. {: note}

14 November 2022

{: #secrets-manager-nov1422} {: release-note}

Manually configure your own DNS provider : If you work with a DNS provider that is not currently integrated with the service, you can manually configure it when you use the {{site.data.keyword.secrets-manager_short}} UI to order new certificates. If you choose to manually configure a provider, you must complete a challenge to prove ownership over your domain. For more information, see Ordering public certificates with your own DNS provider in the UI.

Create a leaf certificate with a certificate signing request : You can create private leaf certificates through your public key infrastructure (PKI) by using a certificate signing request (CSR). Learn more.

18 October 2022

{: #secrets-manager-oct1822} {: release-note}

Version custom metadata : The ability to provide metadata for a specific version of a secret is now available in the UI, in addition to providing metadata for all versions. To learn more about the latest updates, see Creating secrets and Managing secret versions.

Automatic rotation for IAM credentials : The ability to schedule an automatic rotation policy is now available for IAM credentials that are configured for reuse in the UI. For more information, see Automatically rotating secrets.

19 September 2022

{: #secrets-manager-sept1922} {: release-note}

CLI plug-in version 0.1.23 : Version 0.1.23 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

Automatic rotation for IAM credentials : The ability to schedule an automatic rotation policy is now available for IAM credentials that are configured for reuse. For more information, see Automatically rotating secrets.

Manually configure your own DNS provider : If you work with a DNS provider that is not currently integrated with the service, you can manually configure it when you use the {{site.data.keyword.secrets-manager_short}} API to order new certificates. If you choose to manually configure a provider, you must complete a challenge to prove ownership over your domain. For more information, see Ordering public certificates with your own DNS provider.

12 September 2022

{: #secrets-manager-sept1222} {: release-note}

CLI plug-in version 0.1.22 : Version 0.1.22 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

New custom metadata fields : The documentation for creating secrets and managing versions of a secret is now updated to include custom_metadata and version_custom_metadata fields. To learn more about the latest updates, see Creating secrets and Managing secret versions.

New {{site.data.keyword.secrets-manager_short}} event notifications : The following notifications for events related to Secret Locks are now available.

secret_deletion_blocked: Now available for arbitrary secrets, IAM credentials, user credentials, key value, imported certificates, private certificates, and public certificates.
secret_revocation_blocked: Now available for private certificates.
secret_rotation_blocked: Now available for arbitrary secrets, IAM credentials, user credentials, key value, imported certificates, private certificates, and public certificates.
secret_expiration_blocked: Now available for arbitrary secrets, IAM credentials, and user credentials.
secret_version_data_deleted: Now available for arbitrary secrets, IAM credentials, user credentials, key value, imported certificates, private certificates, and public certificates.

For more information about using {{site.data.keyword.en_short}} to enable lifecycle notifications for your {{site.data.keyword.secrets-manager_short}} instance, see Enabling event notifications.

1 August 2022

{: #secrets-manager-aug0122} {: release-note}

Improved authorization flow : The documentation for granting service access to domains is now updated to simplify the required flow. To try out the latest updates, see Granting service access to CIS.

27 July 2022

{: #secrets-manager-jul2722} {: release-note}

CLI plug-in version 0.1.21 : Version 0.1.21 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

10 July 2022

{: #secrets-manager-jul1022} {: release-note}

Lock secrets to prevent them from being deleted : You can now attach locks to secrets to indicate that they're in use by one or more consumers. When a secret is locked, it can't be modified or deleted. For more information, check out the following resources:

- [Locking secrets](/docs/secrets-manager?topic=secrets-manager-secret-locks)
- [Best practices for rotating and locking secrets](/docs/secrets-manager?topic=secrets-manager-best-practices-rotate-secrets)

CLI plug-in version 0.1.20 : Version 0.1.20 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

8 June 2022

{: #secrets-manager-jun822} {: release-note}

Allow access to {{site.data.keyword.secrets-manager_short}} in a restricted account : Working in an account that has IP address access restrictions? To use certain features in {{site.data.keyword.secrets-manager_short}}, for example, to generate IAM credentials, a configuration step is required to ensure that your account is able to accept incoming requests from the service. If your account allows access to only specific IP addresses, you can update your account settings to specify a required list of IP addresses for {{site.data.keyword.secrets-manager_short}}.

27 May 2022

{: #secrets-manager-may2722} {: release-note}

Integration with {{site.data.keyword.alb_full}} : You can now use {{site.data.keyword.secrets-manager_short}} to centrally manage the SSL/TLS certificates that are required for load balancers to perform SSL offloading tasks. To learn more about this integration, check out the {{site.data.keyword.alb_full}} documentation{: external}.

16 May 2022

{: #secrets-manager-may1622} {: release-note}

Updated {{site.data.keyword.secrets-manager_short}} event notifications : Previously, notifications for {{site.data.keyword.secrets-manager_short}} were supported for certificates only. Now, you can be notified when other types of secrets in your instance are expired or soon to expire.

secret_about_to_expire: Now available for arbitrary secrets, IAM credentials, and user credentials.
secret_expired: Now available for arbitrary secrets, IAM credentials, and user credentials.

For more information about using {{site.data.keyword.en_short}} to enable lifecycle notifications for your {{site.data.keyword.secrets-manager_short}} instance, see Enabling event notifications.

CLI plug-in version 0.1.19 : Version 1.1.19 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

25 April 2022

{: #secrets-manager-apr2522} {: release-note}

Create private SSL/TLS certificates for your applications : You can now use {{site.data.keyword.secrets-manager_short}} to set up a private certificate authority (CA) that you can use to issue SSL/TLS certificates to your internal applications. By configuring root and intermediate CAs for your instance, you can establish a valid chain of trust for your certificates. To find out more about this release, check out the announcement blog{: external}.

Preparing to create private certificates
Creating root certificate authorities
Creating intermediate certificate authorities
Adding certificate templates
Creating private certificates

New {{site.data.keyword.secrets-manager_short}} event notifications : The following {{site.data.keyword.secrets-manager_short}} events can now be forwarded to a connected {{site.data.keyword.en_short}} instance.

secret_deleted: Currently supported for imported certificates, private certificates, and public certificates.
secret_revoked: Currently supported for private certificates only.

For more information about using {{site.data.keyword.en_short}} to enable lifecycle notifications for your {{site.data.keyword.secrets-manager_short}} instance, see Enabling event notifications.

CLI plug-in version 1.1.18 : Version 1.1.18 of the {{site.data.keyword.secrets-manager_short}} CLI is now available for download. To learn about the latest updates, see the CLI change log.

11 April 2022

{: #secrets-manager-apr1122} {: release-note}

Integrations with {{site.data.keyword.containershort}} and {{site.data.keyword.openshiftshort}} : You can now use {{site.data.keyword.secrets-manager_short}} to centrally manage Ingress subdomain certificates and other secrets for your Kubernetes or {{site.data.keyword.openshiftshort}} clusters. To learn more about this integration, check out the {{site.data.keyword.containershort}}{: external} or {{site.data.keyword.openshiftshort}} documentation{: external}.

23 March 2022

{: #secrets-manager-mar2322} {: release-note}

Standard and Trial pricing plans : You can now create an unlimited number of {{site.data.keyword.secrets-manager_short}} service instances by choosing the Standard pricing plan. For more information about pricing in {{site.data.keyword.secrets-manager_short}}, check out the announcement blog{: external}.

If you're an existing {{site.data.keyword.secrets-manager_short}} Lite plan user, be sure to upgrade your instance to the Standard plan before 22 May 2022 if you'd like to maintain access. For more information, see the previous release note. {: important}

Osaka and Toronto availability : You can now create a {{site.data.keyword.secrets-manager_short}} service instance in the Osaka (jp-osa) and Toronto (ca-tor) regions.

For more information, see Regions and endpoints.

28 February 2022

{: #secrets-manager-feb2822} {: release-note}

Sao Paulo availability : You can now create a {{site.data.keyword.secrets-manager_short}} service instance in the Sao Paulo (br-sao) region.

For more information, see Regions and endpoints.

23 February 2022

{: #secrets-manager-feb2322} {: release-note}

Pricing plan updates coming soon in {{site.data.keyword.secrets-manager_short}} : On 23 March 2022, {{site.data.keyword.secrets-manager_short}} will introduce Standard and Trial pricing plans. With the introduction of the new plans, the current Lite plan option is deprecated.

Types of plans:

When you provision an instance of the service after the 23 March, you can choose either a Trial or Standard plan.

Trial: To try out the service, you can provision an instance of the service to access all the features that {{site.data.keyword.secrets-manager_short}} offers for a limited time. After the trial period, all functionality is disabled but the instance remains in your account for an additional 30 days, during which you can choose to upgrade your plan. If you choose not to, the instance and its data are automatically removed from your account without any action on your part.

You can have one instance of the service on the trial plan that is provisioned in your account at any time. {: note}

Standard: When you're ready to upgrade, you get unlimited access to all the features that the service offers. The number of instances that your teams can provision is unlimited. With the Standard plan, you are charged per secret and per instance that is provisioned. To view the most current pricing information, see the {{site.data.keyword.secrets-manager_short}} UI.

Important dates:

Be sure to keep the following dates in mind:

23 March 2022: Instances of {{site.data.keyword.secrets-manager_short}} on the Lite plan will be deprecated. As an existing user, you can continue to use the service without interruption, but you should upgrade your instances to the Standard plan as soon as you can after this date.
22 May 2022: Instances of {{site.data.keyword.secrets-manager_short}} on the Lite plan will be disabled and functionality is removed. However, the instance remains in your account for an additional 30 days, during which you can choose to upgrade your plan.
21 June 2022: If you have chosen not to upgrade your plan, the instances of the service and their data will be removed from your account.

Users will have the option to upgrade their service starting 23 March 2022. To ensure that your service functionality is not disrupted, be sure to upgrade to a Standard plan before 22 May 2022. {: important}

3 February 2022

{: #secrets-manager-feb0322} {: release-note}

Enable lifecycle notifications for your certificates : You can now integrate with the {{site.data.keyword.en_short}}{: external} service so that you can manage and route all of your {{site.data.keyword.secrets-manager_short}} alerts to your preferred destinations.

Currently, {{site.data.keyword.secrets-manager_short}} supports notifications for certificates only. For more information, see Enabling event notifications. {: note}

31 January 2022

{: #secrets-manager-jan3122} {: release-note}

Store key-value secrets : You can now create key-value secrets with the {{site.data.keyword.secrets-manager_short}} UI and API. For more information, see Storing key-value secrets.

22 November 2021

{: #secrets-manager-nov2221} {: release-note}

View the version history of your secrets : With the {{site.data.keyword.secrets-manager_short}} UI, you can now check the version history of your secrets so that you can quickly understand when a secret was last rotated. For more information, see Viewing your version history.

Create IAM credentials by using a service ID in your account : In addition to using access groups to determine the access capabilities of an IAM credential, you can now create a secret by using an existing service ID in your account. You can choose this option if you need {{site.data.keyword.secrets-manager_short}} to dynamically generate and manage an API key only.

For more information, see Creating IAM credentials.

Restore secrets to a previous version : Need to roll back a secret to its previous version? If you need to revert a secret, you can now restore select secret types to a previous version.

Currently, you can restore 1 version back for IAM credentials and public certificate secrets only. For more information, see Restoring secrets to a previous version. {: note}

Rotate IAM credentials on-demand : You can now rotate IAM credentials manually by using the UI or APIs. For more information, see Rotating secrets manually.

20 September 2021

{: #secrets-manager-sept2021} {: release-note}

Order domain-validated TLS certificates from Let's Encrypt : In addition to importing your existing certificates, you can now use {{site.data.keyword.secrets-manager_short}} to order domain-validated certificates!

In this release, the following certificate authorities (CA) and DNS providers are supported:

Let's Encrypt
{{site.data.keyword.cloud_notm}} Internet Services (CIS)
{{site.data.keyword.cloud_notm}} classic infrastructure (SoftLayer)

For more information, see Ordering domain-validated certificates from third-parties or check out the announcement blog{: external}.

30 August 2021

{: #secrets-manager-aug3021} {: release-note}

Migrate certificates from {{site.data.keyword.cloudcerts_short}} to {{site.data.keyword.secrets-manager_short}} : Ready to try {{site.data.keyword.secrets-manager_short}} for certificates management? You can now take advantage of automation scripts that can help you to move certificates from {{site.data.keyword.cloudcerts_short}} to {{site.data.keyword.secrets-manager_short}}.

For more information, check out the migration scripts in GitHub{: external}.

20 June 2021

{: #secrets-manager-jun2021} {: release-note}

Import and manage your existing TLS certificates : Looking for the ability to centralize TLS certificates into a single secrets management service? You can now use {{site.data.keyword.secrets-manager_short}} to import TLS certificates that are issued by external certificate authorities (CA).

For more information, check out Importing TLS certificates.

Connect to {{site.data.keyword.secrets-manager_short}} from your VPC network : You can now connect to a {{site.data.keyword.secrets-manager_short}} service instance by using Virtual Private Endpoints (VPE) for VPC.

To learn how to connect your existing {{site.data.keyword.secrets-manager_short}} instance, see Regions and endpoints. For more information about setting up a virtual private endpoint gateway, check out About virtual private endpoint gateways.

19 May 2021

{: #secrets-manager-may1921} {: release-note}

Upcoming updates to supported cipher suites : On 29 May 2021, {{site.data.keyword.secrets-manager_short}} will deliver changes to the cipher suites that it supports for TLS connections to the service. This update is being implemented to enhance the security of IBM Cloud users and protect user data.

What's changing? Beginning 29 May 2021, {{site.data.keyword.secrets-manager_short}} API endpoints will allow only the following cipher suites:
- ECDHE-ECDSA-AES128-GCM-SHA256
- ECDHE-ECDSA-CHACHA20-POLY1305
- ECDHE-ECDSA-AES256-GCM-SHA384
- ECDHE-RSA-AES128-GCM-SHA256
- ECDHE-RSA-CHACHA20-POLY1305
- ECDHE-RSA-AES256-GCM-SHA384
How will this change impact my environment? This change impacts clients that are configured to use ciphers that are not included on this list. To avoid connectivity issues with {{site.data.keyword.secrets-manager_short}}, make sure that your client is configured to use only the allowed list of ciphers in TLS connections to the service. Reach out to IBM Cloud support with any questions.

Manage secrets in your {{site.data.keyword.contdelivery_short}} toolchain : You can now configure {{site.data.keyword.secrets-manager_short}} to securely manage secrets that are part of your {{site.data.keyword.contdelivery_short}} toolchain.

For more information, check out the announcement blog{: external}.

22 March 2021

{: #secrets-manager-mar2221} {: release-note}

Manage secrets over a private network connection : You can now create a private instance of {{site.data.keyword.secrets-manager_short}} so that you can manage application secrets over a private network connection.

For more information, see Securing your connection to {{site.data.keyword.secrets-manager_short}}.

Reuse API keys for IAM credential secrets : By default, IAM credential secrets are generated and deleted each time that the secret is read or accessed. By using the reuse_api_key parameter in the API, or the Reuse IAM credentials option in the UI, you can control whether the associated service ID API key can be reused until the secret expires.

For more information, see Creating IAM credentials.

Analyze {{site.data.keyword.secrets-manager_short}} logs with {{site.data.keyword.la_full_notm}} : {{site.data.keyword.secrets-manager_short}} is now integrated {{site.data.keyword.la_short}} so that you can diagnose issues and analyze logs that are generated by your {{site.data.keyword.secrets-manager_short}} service instance.

For more information, see Viewing logs for {{site.data.keyword.secrets-manager_short}}.

London, Tokyo, and Washington DC availability : {{site.data.keyword.secrets-manager_short}} is now available in the London (eu-gb), Tokyo (jp-tok), and Washington DC (us-east) regions.

For more information, see Regions and endpoints.

15 February 2021

{: #secrets-manager-feb1521} {: release-note}

Now available: {{site.data.keyword.secrets-manager_short}} Java SDK : You can now use the {{site.data.keyword.secrets-manager_full_notm}} Java SDK to connect to your {{site.data.keyword.secrets-manager_short}} service instance.

For more information, check out the {{site.data.keyword.secrets-manager_full_notm}} Java SDK repository in GitHub{: external}.

27 January 2021

{: #secrets-manager-jan2721} {: release-note}

Now available: {{site.data.keyword.secrets-manager_short}} Go and Python SDKs : You can now use the {{site.data.keyword.secrets-manager_full_notm}} Go and Python SDKs to connect to your {{site.data.keyword.secrets-manager_short}} service instance.

For more information, check out the SDK repositories in GitHub:

{{site.data.keyword.secrets-manager_full_notm}} Go SDK{: external}
{{site.data.keyword.secrets-manager_full_notm}} Python SDK{: external}

18 December 2020

{: #secrets-manager-dec1820} {: release-note}

Announcing {{site.data.keyword.secrets-manager_short}} general availability : {{site.data.keyword.secrets-manager_short}} is now generally available in the {{site.data.keyword.cloud_notm}} catalog!

To find out more about this release, check out the announcement blog{: external}.

15 December 2020

{: #secrets-manager-dec1520} {: release-note}

Sydney availability : You can now create a {{site.data.keyword.secrets-manager_short}} service instance in the Sydney (au-syd) region.

For more information, see Regions and endpoints.

14 December 2020

{: #secrets-manager-dec1420} {: release-note}

Now available: {{site.data.keyword.secrets-manager_short}} CLI plug-in : The {{site.data.keyword.secrets-manager_short}} CLI plug-in is now available for download!

You can use the {{site.data.keyword.secrets-manager_short}} CLI to interact with the secrets that you store in your {{site.data.keyword.secrets-manager_short}} instance. To install the plug-in, log in to the IBM Cloud CLI and run ibmcloud plugin install secrets-manager.

To see CLI usage examples for creating secrets of different types, check out Creating secrets.
To find out more about the CLI commands and options that are available for {{site.data.keyword.secrets-manager_short}}, see the CLI reference.

24 November 2020

{: #secrets-manager-nov2420} {: release-note}

Now available: {{site.data.keyword.secrets-manager_short}} Node.js SDK : You can now use the {{site.data.keyword.secrets-manager_full_notm}} Node.js SDK to connect to your {{site.data.keyword.secrets-manager_short}} service instance.

For more information, check out the {{site.data.keyword.secrets-manager_full_notm}} Node.js SDK repository in GitHub{: external}.

13 November 2020

{: #secrets-manager-nov1320} {: release-note}

Now available: {{site.data.keyword.cloud_notm}} plug-ins for Vault : Need to manage {{site.data.keyword.cloud_notm}} secrets by using an on-premises Vault? You can now integrate stand-alone {{site.data.keyword.cloud_notm}} plug-ins for Vault. These open source plug-ins can be used independently from each other so that you can manage {{site.data.keyword.cloud_notm}} secrets through your on-premises Vault server.

To set up authentication between Vault and your {{site.data.keyword.cloud_notm}} account, you can use the {{site.data.keyword.cloud_notm}} Auth Method plug-in for Vault{: external}.
To dynamically create API keys for {{site.data.keyword.cloud_notm}} service IDs, you can use the {{site.data.keyword.cloud_notm}} Secrets Backend plug-in for Vault{: external}.

For more information, check out the announcement blog{: external}

9 November 2020

{: #secrets-manager-nov0920} {: release-note}

Grant controlled access to secret data with the SecretsReader role : You can now choose between the Reader and SecretsReader IAM roles for better control over access to the payload of your secrets.

As a reader, you can browse a high-level view of secrets in your instance. Readers can't access the payload of a secret.
As a secrets reader, you can browse a high-level view of secrets, and you can access the payload of a secret. A secrets reader can't create secrets or modify the value of an existing secret.

To learn more about service access roles, see Managing IAM access for {{site.data.keyword.secrets-manager_short}}.

24 September 2020

{: #secrets-manager-sept2420} {: release-note}

Introducing {{site.data.keyword.secrets-manager_short}} : With {{site.data.keyword.secrets-manager_full_notm}}, you can create secrets dynamically and lease them to applications while you control access from a single location. Built on open source HashiCorp Vault, {{site.data.keyword.secrets-manager_short}} helps you get the data isolation of a dedicated environment with the benefits of a public cloud.

In this release, {{site.data.keyword.secrets-manager_short}} offers support for the following types of secrets:

IAM credentials, which consist of a service ID and API key that are generated dynamically on your behalf.
Arbitrary secrets, such as custom credentials that can be used to store any type of structured or unstructured data.
User credentials, such as usernames and passwords that you can use to log in to applications.

To find out more about capabilities and use cases for {{site.data.keyword.secrets-manager_short}}, check out the announcement blog{: external}.

Files

releases.md

Latest commit

History

releases.md

File metadata and controls

Release notes for {{site.data.keyword.secrets-manager_short}}

13 January 2025

19 November 2024

7 October 2024

23 September 2024

12 August 2024

3 June 2024

13 May 2024

18 March 2024

11 March 2024

12 February 2024

10 January 2024

11 December 2023

4 December 2023

6 November 2023

20 September 2023

19 April 2023

17 April 2023

3 March 2023

11 December 2022

14 November 2022

18 October 2022

19 September 2022

12 September 2022

1 August 2022

27 July 2022

10 July 2022

8 June 2022

27 May 2022

16 May 2022

25 April 2022

11 April 2022

23 March 2022

28 February 2022

23 February 2022

3 February 2022

31 January 2022

22 November 2021

20 September 2021

30 August 2021

20 June 2021

19 May 2021

22 March 2021

15 February 2021

27 January 2021

18 December 2020

15 December 2020

14 December 2020

24 November 2020

13 November 2020

9 November 2020

24 September 2020