[jira] [Commented] (PROTON-1570) SASL auth with GSSAPI fails: client isn't sending correct AMQP header even though SASL is explicitly enabled

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (PROTON-1570) SASL auth with GSSAPI fails: client isn't sending correct AMQP header even though SASL is explicitly enabled

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/PROTON-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163637#comment-16163637 ]

ASF subversion and git services commented on PROTON-1570:
---------------------------------------------------------

Commit 1d36257c9425d57f90c7e68db3e1932701ac530e in qpid-proton's branch refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1d36257 ]

PROTON-1570: [C++ binding] fix connection_option processing
- Previously SASL options (and others) were only processed if they
  were specified as default options on a container


> SASL auth with GSSAPI fails: client isn't sending correct AMQP header even though SASL is explicitly enabled
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-1570
>                 URL: https://issues.apache.org/jira/browse/PROTON-1570
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding
>    Affects Versions: proton-c-0.18.0
>         Environment: commit e631bf6b11960d9687d42dfdde1ff4c65804981c (upstream/master)                                                                                                                                                                                                              
> Author: Andrew Stitcher <[hidden email]>                                                                                                                                                                                                                                
> Date:   Thu Aug 31 17:31:17 2017 -0400                                                                                                                                                                                                                                        
>     PROTON-1567: Implement failover urls
>     - Example "reliable" client sending and receiving messages
>     - Also add jitter to retry backoff (with C++11)
>            Reporter: Jiri Danek
>            Assignee: Andrew Stitcher
>             Fix For: proton-c-0.18.0
>
>
> 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
> {noformat}
> $ 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
> {noformat}
> I am able to connect to the same server with Qpid JMS client without problems.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]