-
Bug
-
Resolution: Done
-
Blocker
Following the product docs [1], we are configuring SSL with env variables HTTPS_NAME, HTTPS_KEYSTORE and HTTPS_PASSWORD as documented in [2] to deploy an EAP secured application - actually the RH-SSO quickstarts, i.e. based on the eap74-https-s2i template and latest JDK 17 based images [3].
The server starts with a WARN about partial HTTPS configuration and unavailability:
... 2022-05-23 07:55:57 Launching EAP Server INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT. INFO Configuring JGroups discovery protocol to dns.DNS_PING INFO Using Elytron for SSL configuration. [0;33mWARN Partial HTTPS configuration, the https connector WILL NOT be configured. Missing: HTTPS_KEYSTORE_TYPE[0m INFO Access log is disabled, ignoring configuration. [0;33mWARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release.[0m [0;33mWARN If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true.[0m INFO Server started in admin mode, CLI script executed during server boot. INFO Running jboss-eap-7-tech-preview/eap74-openjdk17-runtime-openshift-rhel8 image, version 7.4.5 ...
Setting this issue to Blocker since it is breaking backward compatibility.
BTW - although the initial WARN is disappearing when setting HTTPS_KEYSTORE_TYPE=PKCS12, the deployment would fail anyway, complaining about missing KEYCLOAK authentication mechanism. This has been reported as WFWIP-462
- clones
-
WFLY-15622 WARN Partial HTTPS configuration, the https connector WILL NOT be configured. Missing: HTTPS_KEYSTORE_TYPE
- Resolved
- is cloned by
-
JBEAP-24017 [7.4.* JDK 17 images] - Missing required KEYCLOAK mechanism
- Pull Request Sent