Add and Use a Custom Secrets Manager

Updated 2 weeks ago by Chakravarthy Tenneti

Currently, this feature is behind a Feature Flag. Contact Harness Support to enable the feature.

Harness provides first-class support and built-in integration for some of the third party Secret Managers. You can configure and make use of other Secrets Managers using the Custom Secrets Manager. It's a shell script that you can execute anywhere that fetches the secret and shares it with Harness. It can be run on a Delegate or a remote machine connected to a Delegate.

In this topic:

Before You Begin

Step 1. Create an Encrypted Text Secret

Using a configured Secrets Manager, create an Encrypted Text secret to access the third party Secrets Manager.

For more information on creating Encrypted Text Secret, see Add Encrypted Text.

Make sure that the secret you create to access your third party Secrets Manager is selected as Scope to Account. It will not be used for any Application.

Step 2: Add Connection Attributes for Target Hosts

If you want to run the Shell Script on a target host and not on the Harness Delegate, you must first create the required connection attributes.

  • To access an SSH-based Custom Secrets Manager, create an SSH credential first. See Add SSH Keys for the procedure to create SSH credentials.
  • To access a WinRM-based Custom Secrets Manager, create a WinRM connection first. See Add WinRM Connection Credentials for more information.

This does not apply if you want to run the Custom Secrets Manager on the Harness Delegate.

Step 3. Create a Shell Script Template

Create a Shell Script Template. For more information on creating a Shell Script Template and adding it to the Template Library, see Create Shell Script Template.

Note the following points while creating the template.

  • The variable in the Shell Script Template that gets the value must be named secret.
  • Custom secret manager does not support dynamic or runtime values for the variables. All parameters/variables are static and pre-defined. For example, users cannot pass ${workflow.variable...} or ${env.name} to the Shell Script Template.

Here’s an example Shell Script Template created for Custom Secrets Manager.

In this example, this script assigns the secret variable to your final value. Here are the details of the entries in the script.

  • This script makes a cURL call to the API URL of the third party Secrets Manager and gets the output to the file secret.json. 
  • It includes some parameters such as engine name and path. 
  • It uses an existing, already configured Secrets Manager for the API access.
  • After getting the file, as shown in the example, it gets the secret by using a third party tool like jq to retrieve the key from the data object. The key is also a parameter that can be assigned later.

All the parameters (engine name, path, and key in this case) can be defined as Variables while creating or editing the Shell Script Template.

Note: Template library add ons like default variable values, script output, and default timeout are not supported in Custom Secrets Manager configuration.

Step 4. Configure Custom Secrets Manager

Make sure you enter the following details.

Display Name

Enter a name for the Custom Secrets Manager.

Shell Script

Select the Shell Script from the Template Library that you have created for running the Custom Secrets Manager.

Execute on Delegate

Select this if you want to run the Shell Script on Harness Delegate. 

If you want to run it in another host, enter the following details.

Target Host

Enter the name of the Target Host.

Templatize Connection Attribute

If you select this option, the Connection Attribute will be a part of the Test Variables. 

For example, on a single target host, if you want to access different secrets with different keys for different users with a single Shell Script, you can templatize the connection attribute and enter its value while creating the secret.

Connection Attribute

Select an SSH key/WinRM Connection Credential to access the Target Host.

Working Directory

Enter the path to the directory on the Target Host.

Test Variables

Enter test values for the variables defined while creating the Shell Script Template. You must enter these values to verify if the custom Secrets Manager can be accessed and the script within can be executed to get the secret value. You can use a dummy secret or one of the secrets that are already configured for this validation.

Step 5. Use the Custom Secrets Manager

Create an Encrypted Text using the Custom Secrets Manager you created earlier. Enter the name and values of all the Input Variables defined while creating the Shell Script Template. 

For more information on creating Encrypted Text Secret, see Add Encrypted Text.

If you want to create a secret on a Target Host Custom Secrets Manager, you must also select the Connection Attribute.

Limitations

You cannot migrate secrets to or from custom Secrets Managers.


How did we do?