[
https://issues.apache.org/jira/browse/ARTEMIS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835785#comment-17835785
]
Timothy A. Bish commented on ARTEMIS-209:
-----------------------------------------
About the same place as before, proton-j still does this but I don't see it
being changed. There is protonj2 now but there is no effort to replace the
existing protocol head so the issue continues to exist in the broker as before.
> [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: Charles E. Rolke
> Assignee: Timothy A. Bish
> Priority: Major
>
> 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
(v8.20.10#820010)
