You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/08/26 00:58:46 UTC
[jira] [Commented] (ARTEMIS-209) [AMQP] Broker sends frames after
SASL failure
[ https://issues.apache.org/jira/browse/ARTEMIS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712138#comment-14712138 ]
ASF subversion and git services commented on ARTEMIS-209:
---------------------------------------------------------
Commit 4b79ddb0bd02f0a6913beb2f5d7aabf350933543 in activemq-artemis's branch refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=4b79ddb ]
ARTEMIS-209 fix keepAlive
- Received should be set to true on any package
> [AMQP] Broker sends frames after SASL failure
> ---------------------------------------------
>
> Key: ARTEMIS-209
> URL: https://issues.apache.org/jira/browse/ARTEMIS-209
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 1.0.0
> Environment: SASL negotiation over AMQP
> Reporter: Chuck Rolke
>
> The client sends bogus credentials to the Artemis server. The server correctly fails with sasl.outcome code: auth(1). So far so good. Then the server sends an AMQP protocol negotiation frame as if everything was OK.
> After failing SASL the server should close the connection.
> Trace file: https://people.apache.org/~chug/artemis/20150821-1/artemis-sasl-fail-but-sends-amqp-header.html
> From the trace:
> {noformat}
> 10.10.1.1:1340 -> 10.10.10.254:5672 -> init SASL (3): (1.0.0)
> 10.10.1.1:1340 -> 10.10.10.254:5672 -> method sasl.init
> 10.10.1.1:1340 <- 10.10.10.254:5672 <- init SASL (3): (1.0.0), method sasl.mechanisms, method sasl.outcome
> 10.10.1.1:1340 <- 10.10.10.254:5672 <- init AMQP (0): (1.0.0)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)