Configuring Engineering Lifecycle Management instance for TLSv1.2

You can enable the TLSv1.2 or only TLSv1.3 to secure the Engineering Lifecycle Management server and configure the Engineering Lifecycle Management server. Complete the following steps to configure Engineering Lifecycle Management instance with TLSv1.2 or only TLSv1.3.

1. Create an SSL configuration JSON file name as appconfig and save it on your computer. The following code block provides an example of the application configuration definition JSON file with only TLSv1.3.

   {
       "common": {
           "security": {
               "SSL_PROTOCOL": "TLSv1.3",
               "SSL_CIPHERS": "CIPHER1 CIPHER2" 
           }
       },
       "appSpecific": {
           "JTS":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "QM":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "RM":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "CCM":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "GC":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "DCC":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "ENI":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "RB":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "LQE":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "LDX":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3", 
               "SSL_CIPHERS":  "CIPHER1 CIPHER2" 
               } 
           },
           "JAS":  { 
               "security": {
               "SSL_PROTOCOL": "TLSv1.3"
               } 
           }
       }
   }

   common > security > SSL_PROTOCOL

   (Optional) The common SSL protocol applied for all Engineering Lifecycle Management applications. Supported values are

   1. TLSv1.2
   2. TLSv1.2-strict
   3. TLSv1.3
   4. TLSv1.2,TLSv1.3 (Default value)

   common > security > SSL_CIPHERS

   (Optional) Define the list of ciphers that you applied for all Engineering Lifecycle Management applications.

   appSpecific >{app name}> security >SSL_PROTOCOL

   (Optional) The common SSL protocol you would like to apply for all Engineering Lifecycle Management applications. Supported values are

   1. TLSv1.2
   2. TLSv1.2-strict
   3. TLSv1.3
   4. TLSv1.2,TLSv1.3 (Default value)

   appSpecific >{app name}> security >SSL_CIPHERS IDER_USERID

   (Optional) Define the list of ciphers that you would like to apply for all Engineering Lifecycle Management applications. Note: This value would override the common security SSL_CIPHERS value for the specified application

2. Create the configmap by using the following methods. It creates the user defined configmap. Example elm-application-config in the project.
   Red Hat Openshift Container Platform web console

   1. Go to Workloads > ConfigMaps.
   2. Select Create configmap on the upper right of the page.
   3. To continue by using the Form view
      • Enter the configmap contents: name:elm-application-config
      • Add the key appconfig and for value, browse local json file to upload.
      • Click on Create.
   Command for Red Hat Openshift CLI

   oc create configmap elm-application-config --from-file=<folder-path>/appconfig

   Command for Kubernetes CLI

   kubectl create configmap elm-application-config --from-file=<folder-path>/appconfig

3. Define the configmap name in Engineering Lifecycle Management instance yaml with following specification: appConfigName Configmap name created in step 2

   apponfigName: <config-map-name>

   For more information, see Template and sample YAML of ConfigMap