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

wildfly-config.xml should not be required

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7295 Remote method invocation fails in ejb-security-interceptors quickstart

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9718 AuthenticationContext is not properly propagated in ejb client when using jboss-ejb-client.properties

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7415 Missing XSD for wildfly-config.xml

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: