search

wls-eng / arm-oraclelinux-wls

Microsoft Azure ARM Templates to create Oracle Linux VM with pre-installed Weblogic Server
Apache License 2.0
0 stars 7 forks source link

Modify nodemanager SSL configuration to support strict checking by JDK11 and other higher versions of JDK #253

Closed gnsuryan closed 3 years ago

gnsuryan commented 3 years ago

JDK11 and other higher versions of JDK have strict checks regarding SSL configuration and therefore require more specific information to be configured in the nodemanager configuration.

As per Weblogic Server Documentation for SSL configuration for NodeManager, (Refer https://docs.oracle.com/en/cloud/paas/java-cloud/jscug/configure-ssl-weblogic-server.html#GUID-9AA01706-5782-4C1A-9DFB-603F425D8C78), the following nodemanager SSL configuration properties need to be included.

KeyStores=CustomIdentityAndCustomTrust CustomIdentityKeystoreType=jks CustomIdentityKeyStoreFileName=path_to_identity_keystore CustomIdentityKeyStorePassPhrase=keystore_password CustomIdentityPrivateKeyPassPhrase=server_cert_password CustomIdentityAlias=server_cert CustomTrustKeystoreType=jks CustomTrustKeyStoreFileName=path_to_trust_keystore CustomTrustKeyStorePassPhrase=keystore_password

In the current implementation of WLS on Azure, only few of these SSL configuration parameters have been configured, which might result in nodemanager startup failure when the application is moved to higher versions of JDK.

To fix this issue, these additional SSL configurations have to be included in the nodemanager.properties file.

gnsuryan commented 3 years ago

The changes related to this issue are fixed and merged in to the wls-eng branch for all Configured & Dynamic Cluster offers.

https://github.com/wls-eng/arm-oraclelinux-wls-dynamic-cluster/pull/102

https://github.com/wls-eng/arm-oraclelinux-wls-cluster/pull/120