[ https://issues.apache.org/jira/browse/QPID-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092719#comment-16092719 ]
ASF subversion and git services commented on QPID-7787: ------------------------------------------------------- Commit 83eb7addddab25223bd19ed5c97cdad1a8ea178d in qpid-broker-j's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=83eb7ad ] QPID-7787: [Java Broker] Allow the use of AMQP 1.0 SaslOutcome to additional data to carry SASL final message The current default is to have the final message carried by a Challenge (i.e. unchanged). This will be flipped once ProtonJ/Qpid JMS Client are released. Based on original work of rgodfrey <rgodf...@apache.org> > [Java Broker] In AMQP 1.0 allow the SASL outcome to carry additional > information > -------------------------------------------------------------------------------- > > Key: QPID-7787 > URL: https://issues.apache.org/jira/browse/QPID-7787 > Project: Qpid > Issue Type: Bug > Components: Java Broker > Reporter: Lorenz Quack > Fix For: qpid-java-broker-7.0.0 > > Attachments: > 0001-QPID-7787-Java-Broker-Use-the-AMQP-SaslOutcome-s-add.patch, > QPID_7787___allow_the_SASL_outcome_to_carry_additional_information.patch > > > Currently, when a SASL negotiation is successful but has additional data this > data is sent as a challenge requiring another round-trip. > AMQP 1.0 allows to send additional data in the SASL Outcome frame avoiding > the additional round trip. We should use this in > {{AMQPConnection_1_0Impl#processSaslResponse}}. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org