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

Missing sasl dependencies in jboss-ejb-client through jboss-remoting

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      • build wf boms
      • create custom pom.xml 
        <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.jboss.qa.eap.ejb</groupId>
    <artifactId>ejb-client-dependency-test</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>jar</packaging>

    <properties>
        <maven.compiler.target>11</maven.compiler.target>
        <maven.compiler.source>11</maven.compiler.source>
    </properties>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.wildfly</groupId>
                <artifactId>wildfly-ejb-client-bom</artifactId>
                <version>28.0.0.Beta1-SNAPSHOT</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>org.jboss</groupId>
            <artifactId>jboss-ejb-client</artifactId>
        </dependency>
    </dependencies>
</project>
      • mvn dependency:tree
      Show
      build wf boms git clone https://github.com/wildfly/boms.git . mvn install create custom pom.xml <?xml version= "1.0" encoding= "UTF-8" ?> <project xmlns= "http://maven.apache.org/POM/4.0.0" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" > <modelVersion> 4.0.0 </modelVersion> <groupId> org.jboss.qa.eap.ejb </groupId> <artifactId> ejb-client-dependency-test </artifactId> <version> 1.0-SNAPSHOT </version> <packaging> jar </packaging> <properties> <maven.compiler.target> 11 </maven.compiler.target> <maven.compiler.source> 11 </maven.compiler.source> </properties> <dependencyManagement> <dependencies> <dependency> <groupId> org.wildfly </groupId> <artifactId> wildfly-ejb-client-bom </artifactId> <version> 28.0.0.Beta1-SNAPSHOT </version> <type> pom </type> <scope> import </scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId> org.jboss </groupId> <artifactId> jboss-ejb-client </artifactId> </dependency> </dependencies> </project> mvn dependency:tree

      According to the EAP7-325 RFE, jboss-ejb-client dependency should bring sasl transitive dependencies, if EJB-bom is used a as a dependency-management, this way is still supported according to our documentation and there is no RFE for drop of this feature. EAP 8 beta did this through jboss-remoting 5.0.25.Final:

      [INFO] \- org.jboss:jboss-ejb-client:jar:5.0.1.Final-redhat-00001:compile
...
[INFO]    +- org.jboss.remoting:jboss-remoting:jar:5.0.25.Final-redhat-00001:compile
[INFO]    |  \- org.wildfly.security:wildfly-elytron:jar:2.0.0.Beta2-redhat-00001:compile
...
[INFO]    |     +- org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:2.0.0.Beta2-redhat-00001:compile
...
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-digest:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-entity:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-external:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-gs2:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-gssapi:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-oauth2:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-otp:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-plain:jar:2.0.0.Beta2-redhat-00001:compile
[INFO]    |     +- org.wildfly.security:wildfly-elytron-sasl-scram:jar:2.0.0.Beta2-redhat-00001:compile
...

      Current WF from main branch is using jboss-remoting 5.0.26, where wildfly-elytron is missing and a lot of sasl dependencies as well:

      [INFO] \- org.jboss:jboss-ejb-client:jar:5.0.1.Final:compile
...
[INFO]    +- org.jboss.remoting:jboss-remoting:jar:5.0.26.Final:compile
..
[INFO]    |  |  \- org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:2.0.0.Final:compile
[INFO]    |  \- org.wildfly.security:wildfly-elytron-sasl-auth-util:jar:2.0.0.Final:compile

      REM3-394 removed wildfly-elytron dependency in this commit. This is a regression against EAP 8.0.Beta (so the priority is a blocker). Missing wildfly-elytron removes transitive sasl dependencies, which is also a bug on EAP7-325 RFE.

              tadamski@redhat.com Tomasz Adamski
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: