Open

You will learn

How to install Helm and modify ESAPI properties.

Prerequisites

Audience: IT Professional
Difficulty: Basic
Time needed: Approximately 10 minutes
Tools required: See Pre-requisites list below

Pre-requisites List:

• ThreadFix instance running in Kubernetes

• kubectl access to Kubernetes cluster

• Helm version greater than 3.5

• Bash compatible terminal

Download Default Properties

If the ESAPI.properties file has not been modified, first download the default properties file and setup to current user values.

Enter the following commands on a command line to perform the described action.

1. Get the Helm release name for the ThreadFix instance.

   TF_RELEASE=$(helm ls | grep threadfix | awk '{print $1}')

    

2. Get the current version of ThreadFix.

   TF_VERSION=$(helm ls --filter "$TF_RELEASE" | grep -o 'threadfix-[Az0-9\.\-]*' | sed 's|threadfix-||g')

    

3. Pull the ThreadFix chart locally.

   helm pull denimgroup/threadfix --version $TF_VERSION

    

4. Unzip the ThreadFix chart archive.

    

5. Convert ESAPI.properties to yaml format.

    

6. Export the currently installed Helm values.

    

7. Backup values to a separate file.

    

8. Add default ESAPI.properties to myValues.yaml.

Get Existing Settings

If the ESAPI.properties has already been setup and the user wants to change settings, download the current values from the installation.

1. Get the Helm release name for the ThreadFix instance.

    

2. Get the current installed version of ThreadFix.

    

3. Export the currently installed Helm values.

    

4. Backup values to a separate file.

Make Changes and Apply

1. Change ESAPI settings:

   1. Open myValues.yaml in a text editor.

   2. Locate the 'ESAPI.properties' section.

   3. Edit properties as desired.

   4. Save the file.
      
      

2. Update the ThreadFix Helm installation.

   Note: if not using 'denimgroup/threadfix' as the chart name, this value must be changed to the location of the ThreadFix chart. Use helm search repo threadfix to find the correct chart name.
   
   

3. Restart the ThreadFix deployments.

Table of Contents