qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakub Scholz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-63) SASL ANONYMOUS doesn't seem to work against the C++ broker
Date Tue, 02 Jun 2015 11:32:17 GMT

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

Jakub Scholz commented on QPIDJMS-63:
-------------------------------------

To be honest, I didn't studied the SASL specification - I saw that the behavior was the same
as in QPIDJMS-33 and maybe jumped a bit to the conclusion :-o. But it seems to work with both
modes of the C++ broker as well as the Java broker.

> SASL ANONYMOUS doesn't seem to work against the C++ broker
> ----------------------------------------------------------
>
>                 Key: QPIDJMS-63
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-63
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.2.0
>            Reporter: Jakub Scholz
>            Priority: Minor
>             Fix For: 0.3.0
>
>         Attachments: QPIDJMS-63.patch
>
>
> It looks like the same problem which was described and fixed for SASL EXTERNAL in QPIDJMS-33
is present also for the ANONYMOUS mechanism (broker log): 
> {code}
> 2015-06-01 21:01:59 [Network] info Set TCP_NODELAY on connection to 192.168.1.241:57519
> 2015-06-01 21:01:59 [Broker] info Using AMQP 1.0 (with SASL layer)
> 2015-06-01 21:01:59 [Security] info SASL: Mechanism list: ANONYMOUS
> 2015-06-01 21:01:59 [Protocol] debug qpid.172.17.0.15:5672-192.168.1.241:57519 Sent SASL-MECHANISMS(ANONYMOUS)
31
> 2015-06-01 21:01:59 [Protocol] debug qpid.172.17.0.15:5672-192.168.1.241:57519 writing
protocol header: 1-0
> 2015-06-01 21:01:59 [Protocol] debug qpid.172.17.0.15:5672-192.168.1.241:57519 Received
SASL-INIT(ANONYMOUS, )
> 2015-06-01 21:01:59 [Security] info SASL: Starting authentication with mechanism: ANONYMOUS
> 2015-06-01 21:01:59 [Protocol] debug qpid.172.17.0.15:5672-192.168.1.241:57519 Sent SASL-CHALLENGE()
22
> 2015-06-01 21:01:59 [Security] info qpid.172.17.0.15:5672-192.168.1.241:57519 Challenge
issued
> 2015-06-01 21:02:09 [System] error Connection qpid.172.17.0.15:5672-192.168.1.241:57519
No protocol received after 10s, closing
> 2015-06-01 21:02:09 [Security] info qpid.172.17.0.15:5672-192.168.1.241:57519 Connection
closed prior to authentication completing
> 2015-06-01 21:02:09 [Security] info qpid.172.17.0.15:5672-192.168.1.241:57519 Connection
closed prior to authentication completing
> {code}
> This occurs only when the authentication is enabled in the AMQP broker. When the broker
is started without authentication (--auth=no option) it actually works fine. Only when the
ANONYMOUS mechanism is enabled as a part of the regular authentication, this error appears.
> The solution seems to be the same as in QPIDJMS-33. I.e. setting the initial response
to EMPTY instead of null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message