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

SASL auth with GSSAPI fails: client isn't sending correct AMQP header even though SASL is explicitly enabled

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: proton-c-0.18.0
    • Fix Version/s: proton-c-0.18.0
    • Component/s: cpp-binding
    • Labels:
      None
    • Environment:

      Description

      When using the sample client from https://github.com/ssorj/skylla/blob/master/cpp/connect.cpp to connect to current ActiveMQ Artemis server 2.4.0-SNAPSHOT, I am getting the following error

      $ PN_TRACE_FRM=1 KRB5_TRACE=/dev/stdout LD_LIBRARY_PATH=/var/local/lib64/ ./connect 127.0.0.1
      [0x7b4c00000550]:  -> AMQP
      [0x7b4c00000550]:0 -> @open(16) [container-id="", hostname="127.0.0.1", channel-max=32767]
      [0x7b4c00000550]:0 -> @close(24) [error=@error(29) [condition=:"amqp:connection:framing-error", description="AMQP header mismatch: AMQP SASL layer ['AMQP\x03\x01\x00\x00']"]]
      [0x7b4c00000550]:  <- EOS
      [0x7b4c00000550]:  -> EOS
      terminate called after throwing an instance of 'proton::error'
        what():  amqp:connection:framing-error: AMQP header mismatch: AMQP SASL layer ['AMQP\x03\x01\x00\x00']
      Aborted
      

      I am able to connect to the same server with Qpid JMS client without problems.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                astitcher Andrew Stitcher
                Reporter:
                jdanek Jiri Daněk
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: