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

Remote naming client from EAP 7.0 can't authenticate against EAP 7.1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.DR16
    • 7.1.0.DR13
    • Naming
    • None
    • Regression
    • Hide

      Follow the attached reproducer archive, README included.

      Show
      Follow the attached reproducer archive, README included.

    Description

      When using the jboss-remote-naming library from EAP 7.0 against EAP 7.1.0.DR13 the client is unable to authenticate and all lookups time out ( java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS )

      The exact same client code with the same dependencies works when running against EAP 7.1.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ELY-1005 Incompatible handling of digest-uri from legacy clients.

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-9585 Upgrade WildFly Elytron to 1.1.0.Beta32

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7100 Remoting client from EAP 7.0.0 can't authenticate against EAP 7.1.0.DR8

          • 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

              sdouglas1@redhat.com Stuart Douglas
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: