Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-4121

JBoss EAP 7.4.6 JDK 11 images are missing keycloak configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • EAP74 7.4.6.GA
    • EAP74 7.4.6.GA
    • EAP7
    • None

      After upgrading to JBoss EAP 7.4.6 OpenShift images, the /opt/eap/bin/launch/launch-config.sh misses the keycloak entry:

      sh-4.4$ cat ../version.txt 
      Red Hat JBoss Enterprise Application Platform - Version 7.4.6.GA
      sh-4.4$ cat /opt/eap/bin/launch/launch-config.sh
      #!/bin/sh
      
      # Centralised configuration file to set variables that affect the launch scripts in wildfly-cekit-modules.
      
      # Scripts that modify the configuration. Either via xml marker replacement or via CLI commands.
      # wildfly-cekit-modules will look for each of the listed files and run them if they exist.
      CONFIG_SCRIPT_CANDIDATES=(
        $JBOSS_HOME/bin/launch/backward-compatibility.sh
        $JBOSS_HOME/bin/launch/configure_extensions.sh
        $JBOSS_HOME/bin/launch/passwd.sh
        $JBOSS_HOME/bin/launch/messaging.sh
        $JBOSS_HOME/bin/launch/datasource.sh
        $JBOSS_HOME/bin/launch/resource-adapter.sh
        $JBOSS_HOME/bin/launch/admin.sh
        # Keep this order, jgroups.sh before ha.sh. jgroups.sh is the script which initializes the protocol list store
        # used to share changes in the protocol list when a protocol is added either by ha.sh or by jgroups.sh.
        # This protocol store is just a set of files under temporal directory. We need them to be able to share changes
        # done by the ha.sh and jgroups.sh routines which are executed in subshells
        $JBOSS_HOME/bin/launch/jgroups.sh
        $JBOSS_HOME/bin/launch/ha.sh
        $JBOSS_HOME/bin/launch/https.sh
        $JBOSS_HOME/bin/launch/elytron.sh
        $JBOSS_HOME/bin/launch/json_logging.sh
        $JBOSS_HOME/bin/launch/configure_logger_category.sh
        $JBOSS_HOME/bin/launch/security-domains.sh
        $JBOSS_HOME/bin/launch/jboss_modules_system_pkgs.sh
        $JBOSS_HOME/bin/launch/deploymentScanner.sh
        $JBOSS_HOME/bin/launch/ports.sh
        $JBOSS_HOME/bin/launch/access_log_valve.sh
        $JBOSS_HOME/bin/launch/filters.sh
        $JBOSS_HOME/bin/launch/statefulset.sh
        /opt/run-java/proxy-options
      )
      # The server configuration file to use. If not set, wildfly-cekit-modules defaults to standalone.xml.
      # For EAP we want standalone-openshift.xml
      WILDFLY_SERVER_CONFIGURATION=standalone-openshift.xml
      # The configuration adjustment mode. For EAP we want both xml marker replacement and CLI commands.
      # Notice that the value of this variable must be aligned with the value configured in assemble
      export CONFIG_ADJUSTMENT_MODE="xml_cli"
      

      As a result, keycloak configuration doesn't happen, and the deployment of an application fails with "UT010039: Unknown authentication mechanism KEYCLOAK".

      The $JBOSS_HOME/bin/launch/keycloak.sh script itself is still present.

            kwills@redhat.com Ken Wills
            thofman Tomas Hofman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: