Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-1136

[proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • proton-0.12.0
    • proton-j-future
    • proton-j
    • None

    Description

      Currently Proton-J is unable to handle pipelined SASL and OPEN frames for ANONYMOUS logins, which are currently sent by proton-c, e.g see the below trace log from Dispatch connecting out using ANONYMOUS:

      [0x7f41f80079c0]:  -> SASL
[0x7f41f80079c0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b"anonymous@localhost.localdomain"]
[0x7f41f80079c0]:  -> AMQP
[0x7f41f80079c0]:0 -> @open(16) [container-id="Qpid.Dispatch.Router.A", max-frame-size=65536, channel-max=32767, idle-time-out=8000, offered-capabilities=:"ANONYMOUS-RELAY", properties={:product="qpid-dispatch-router", :version="0.6.0"}]
[0x7f41f80079c0]:  <- SASL
[0x7f41f80079c0]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=:ANONYMOUS]
[0x7f41f80079c0]:0 <- @sasl-outcome(68) [code=0]
[0x7f41f80079c0]:  <- AMQP

      Given that there are various clients using proton that might do this by default (PROTON-1135 raised regarding that), proton-j should be updated to cope with it.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. PROTON-1135 [proton-c] dont pipeline SASL and OPEN frames for ANONYMOUS logins by default

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              gmurthy Ganesh Murthy
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: