Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8574

Unify default wildfly-config.xml across clients (Elytron)

XMLWordPrintable

      Some client facing JARs contains default Elytron client configuration in `META-INF/wildfly-config.xml`:

      bin/client/jboss-cli-client.jar
bin/client/jboss-client.jar
modules/system/layers/base/org/jboss/as/protocol/main/wildfly-protocol-3.0.0.Alpha22-redhat-1.jar
modules/system/layers/base/org/jboss/as/remoting/main/wildfly-remoting-3.0.0.Alpha22-redhat-1.jar
modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-3.0.0.Alpha22-redhat-1.jar
modules/system/layers/base/org/jboss/remoting-jmx/main/remoting-jmx-3.0.0.Beta2-redhat-1.jar
modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-3.0.0.Beta4-redhat-1.jar

      The configuration across the libraries is not unified, which could lead to different configuration used for different classpath ordering.

      The issue is mainly with set of allowed SASL mechanisms across the libraries. Here are fragments of mechanism filtering used in the mentioned files:

      <allow-all-sasl-mechanisms />
<allow-sasl-mechanisms names="JBOSS-LOCAL-USER EXTERNAL DIGEST-MD5 PLAIN ANONYMOUS" />
<allow-sasl-mechanisms names="JBOSS-LOCAL-USER DIGEST-MD5 PLAIN ANONYMOUS" />

              darran.lofthouse@redhat.com Darran Lofthouse
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: