E1: OCI: ORCH: After Enabling TLSv1.3 Protocol for Server Manager Management JMX Communication or on AIS and JAS Instances, Login in Orchestrator Studio Fails With Following Message: "JAS Connection Error - Received fatal alert: handshake failure" (Doc ID 3049871.1)

Last updated on SEPTEMBER 25, 2024

Applies to:

Symptoms

After applying the automated TLS configuration settings for TLSv1.3 in Server Manager Management Console, or after enabling the minimum TLS protocol to TLS v1.3 by adding "-Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.3" startup argument, the Orchestrator Studio login fails with the below message.
The AIS server instances are configured to communicate with a clustered JAS server instances through Load Balancer as a Service (LBaaS) and the virtual host of LBaaS is defined in rest.ini for JasHost under [BASIC CONFIG] stanza.

Also in the e1root log on AIS server the following error is recorded:

Steps to replicate
1. Open the Orchestrator Studio in web browser
2. Fill in the username and the password and click on "Sign In" button
3. The error is popped up on the screen

Changes

Enabled TLS v1.3 for Server Manager Management Console JMX communication through automated TLS configuration, or disabling the weaker TLS protocol and start using TLSv1.3 on AIS and JAS servers, where JAS server instances are behind a Load Balancer as a Service (LBaaS)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.