Configuring Sterling B2B Integrator URLs with TLSv1.3

For IIM

Set the TLS protocol version for the dashboard UI with the jsseProtocol property, which is part of the noapp.properties_platform_ifcresources_ext properties. You can set the below property in the customer_overrides.properties file.
noapp.jsseProtocol=TLS1.3

To make use of TLSv1.3 Ciphers in communication, set TLSv1.3 Ciphers to the dashboardCipherSuite property. The dashboardCipherSuite property is defined in the security.properties_platform_asi_ext. You can set the below property in the customer_overrides.properties.

security.dashboardCipherSuite=TLSv13Ciphers
These are the example URLs:
/dashboard
/mailbox
/filegateway
/myfilegateway
/myfg
/ebicsClient
To use TLSv1.3 with Liberty HTTPS:
  1. Navigate to /<install_dir>/liberty/wlp/usr/servers/SIServer.
  2. Specify the value in server.xml:
    sslProtocol="TLSv1.3"
  3. Navigate to the JVM.options file and add TLSv1.3 to the -Dhttps.protocols parameter as follows:
    -Dhttps.protocols=TLSv1.3
    Note:
    • -Dhttps.protocols accepts multiple values. For example, you can set -Dhttps.protocols=TLSv1.3,TLSv1.2. The highest value will take precedence in the B2BAPIs UI.
    • This configuration is also required for an external trading partner authenticated using TLS 1.3 for myfg 2.0 hosted on a HTTP Server Adapter.
Example URL:
/B2BAPIs/svc

For Certified Container

Configure Sterling B2B Integrator URLs with TLSv1.3 using the customization UI.

  1. Login to the customization UI and navigate to the PropertyFile section.
  2. Open the customer_overrides file and switch to the property tab.
  3. Select Create Property and add the following properties:
    noapp.jsseProtocol=TLS1.3
security.dashboardCipherSuite=TLSv13Ciphers
  4. To use TLSv1.3 with Liberty HTTPS, update the following properties in values.yaml under the setupCfg section: 
    libertyProtocol: TLSv1.3
libertyJvmOptions: "-Dhttps.protocols=TLSv1.3"
    For more information, see Sample values.yaml file.
  5. Perform helm install or upgrade to apply the configuration change:
    helm upgrade <release-name> <path-to-helm-charts> -f values_override.yaml