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

wildfly-config.xml should not be required

XMLWordPrintable

      With client dependencies from EAP 7.1 (Remoting 5 etc.), we noticed that in many cases we had to add a wildfly-config.xml to enable SASL mechanisms on the client side, otherwise the client applications aren't able to authenticate against EAP server. This isn't required when using dependencies from EAP 7.0. For backward compatibility, all valid uses of Remoting/EJB client/naming client, etc. should continue working as-is without needing to include a wildfly-config.xml file.

      Things that broke because of this are linked here.

            Unassigned Unassigned
            jmartisk@redhat.com Jan Martiska
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: