Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-64

[AMQP] Broker does not respond to SASL handshake

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • A-MQ 7.0.0.GA
    • None
    • None
    • Hide

      Run any AMQP client that connects with no SSL but tries to authenticate with SASL. In my case I used Amqp.NET Lite self tests directed to

      public static Address address = new Address("amqp://guest:guest@10.10.63.218:5672");

      If I delete the guest:guest user credentials in the target Address then the client connects without SASL and the Artemis broker starts normally.

      Show
      Run any AMQP client that connects with no SSL but tries to authenticate with SASL. In my case I used Amqp.NET Lite self tests directed to public static Address address = new Address("amqp://guest:guest@10.10.63.218:5672"); If I delete the guest:guest user credentials in the target Address then the client connects without SASL and the Artemis broker starts normally.

    Description

      An AMQP client sends two SASL Handshake frames

       ◊  ◊◊ 5.143770  Frame 276  10.18.96.1:27740  -> 10.10.63.218:5672  ->   init SASL (3): (1.0.0)
   ◊  init SASL (3): (1.0.0)
        Protocol: AMQP
        Protocol-ID: 3
        Version Major: 1
        Version Minor: 0
        Version-Revision: 0
◊  ◊◊ 5.150913  Frame 280  10.18.96.1:27740  -> 10.10.63.218:5672  ->   method sasl.init
   ◊  method sasl.init
        Length: 49
        Doff: 2
        Type: SASL (1)
        Channel: 0
        Method: sasl.init (65)
        Arguments (list of 3 elements)
             Mechanism: PLAIN
             Init-Response: 006775657374006775657374
             Hostname: 10.10.63.218

      The broker does not respond and after a while issues a timeout.

      AMQ212037: Connection failure has been detected: 
AMQ119014: Did not receive data from /10.18.96.1:27740 ...

      The expectation if for the broker to respond to the SASL negotiation.

      Attachments

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-380 Release 7.0.0.ER4 with Hand Off document

          • 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.
          • Closed
          is caused by

          ARTEMIS-500 Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              crolke@redhat.com Chuck Rolke (Inactive)
              Andy Taylor, Chuck Rolke (Inactive)
              Petra Svobodova Petra Svobodova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: