[ https://issues.apache.org/jira/browse/PROTON-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated PROTON-1136: ----------------------------------- Description: 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. was: Currently Proton-J is unable to handle pipelined SASL and OPEN frames. Proton-J should be fixed such that it handles the following scenario {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} Summary: [proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login (was: Proton J must handle the case when pipelined SASL and OPEN frames are sent ) Tweaked description for clarity. > [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)