[jboss-jira] [JBoss JIRA] (REMJMX-139) Unify default wildfly-config.xml across clients (Elytron)

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/REMJMX-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse moved JBEAP-10911 to REMJMX-139:
-------------------------------------------------

              Project: Remoting JMX  (was: JBoss Enterprise Application Platform)
                  Key: REMJMX-139  (was: JBEAP-10911)
             Workflow: classic default workflow  (was: CDW with loose statuses v1)
          Component/s: Security
                           (was: Security)
    Affects Version/s:     (was: 7.1.0.DR11)
        Fix Version/s: 3.0.0.Beta4
                           (was: 7.1.0.DR18)


> Unify default wildfly-config.xml across clients (Elytron)
> ---------------------------------------------------------
>
>                 Key: REMJMX-139
>                 URL: https://issues.jboss.org/browse/REMJMX-139
>             Project: Remoting JMX
>          Issue Type: Bug
>          Components: Security
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>            Priority: Blocker
>              Labels: authentication-client, wildfly-config
>             Fix For: 3.0.0.Beta4
>
>
> Some client facing JARs contains default Elytron client configuration in `META-INF/wildfly-config.xml`:
> {code}
> 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
> {code}
> 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:
> {code:xml}
> <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" />
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)