My Oracle Support Banner

JDeveloper Unable to Deploy Applications to Standalone WebLogic Via SSL (Doc ID 3038823.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle JDeveloper - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

Customer is able to deploy different applications from JDeveloper 12c to FMW 12.2.1.4 servers successfully via the non-SSL port.
But when the "Allow SSL only" checkbox is selected in the server's connection information, SSL handshake errors show up while attempting to deploy.
JDeveloper also shows a little red X on the server name in the IDE Connections view for that server.

The Admin and Managed servers all use the same SSL identity certificate. On the user workstation, a trust store is created that includes:

- Root CA cert
- Intermediate CA cert
- Server's identity cert (public, not private)

This trust store works for other tools connecting to the servers securely, such as SOAP UI. But it is not working with JDeveloper.

This was configured under Tools -> Preferences -> Credentials -> Client Trusted Certificate Keystore (and Password)

In JDeveloper, the IDE connection points to a server and port, which is in the SAN list. Since the CN does not match the server name, we expect JDeveloper to rely on the supported SAN list (where the server is listed).

Is there any chance the JDeveloper doesn't support SSL verification using the SAN list in the cert?

The issue can be reproduced at will with the following steps:
1. Configure the server o use SSL
2. Deploy the application using the SSL port for the server
3. Deployment fails with handshake error

Due to this issue, development is impacted

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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