You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2016/02/17 18:05:18 UTC

[jira] [Commented] (PROTON-1136) [proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login

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

Rob Godfrey commented on PROTON-1136:
-------------------------------------

Presumably this issue is not restricted to ANONYMOUS, but any case where the "client" can pipeline the entire SASL exchange (e.g. EXTERNAL, PLAIN, etc...)

>From the point of view of the spec.. as one of the co-authors I don't think I ever anticipated pipelining then entire SASL interaction and then AMQP operations so it certainly wasn't the intent that every implementation MUST be able to handle the receipt of such... however for certain use cases I can see why you't want to be able to send the entire thing asynchronously so I think we SHOULD handle them... but maybe have a way of turning off such pipelining (through config / connection options / whatever) on the sending side.

> [proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login
> -------------------------------------------------------------------------------------------
>
>                 Key: PROTON-1136
>                 URL: https://issues.apache.org/jira/browse/PROTON-1136
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.12.0
>            Reporter: Ganesh Murthy
>
> Currently Proton-J is unable to handle pipelined SASL and OPEN frames for ANONYMOUS logins, which are currently sent by proton-c, e.g see the below trace log from Dispatch connecting out using ANONYMOUS:
> {code}
> [0x7f41f80079c0]:  -> SASL
> [0x7f41f80079c0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b"anonymous@localhost.localdomain"]
> [0x7f41f80079c0]:  -> AMQP
> [0x7f41f80079c0]:0 -> @open(16) [container-id="Qpid.Dispatch.Router.A", max-frame-size=65536, channel-max=32767, idle-time-out=8000, offered-capabilities=:"ANONYMOUS-RELAY", properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x7f41f80079c0]:  <- SASL
> [0x7f41f80079c0]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=:ANONYMOUS]
> [0x7f41f80079c0]:0 <- @sasl-outcome(68) [code=0]
> [0x7f41f80079c0]:  <- AMQP
> {code}
> Given that there are various clients using proton that might do this by default (PROTON-1135 raised regarding that), proton-j should be updated to cope with it.



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