You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/06/15 17:08:00 UTC
[jira] [Created] (QPIDJMS-73) add support for pipelining SASL init
Robbie Gemmell created QPIDJMS-73:
-------------------------------------
Summary: add support for pipelining SASL init
Key: QPIDJMS-73
URL: https://issues.apache.org/jira/browse/QPIDJMS-73
Project: Qpid JMS
Issue Type: New Feature
Components: qpid-jms-client
Reporter: Robbie Gemmell
In the case where only one option is configured (via QPIDJMS-69) for SASL mechanism, it may also be useful to optionally support pipelining output of the SASL init frame if that is possible (depending on the mechanism, it obviously only works for some, i.e those which dont require a server initiated challenge to begin).
Raised based on comment from [~gtully] on QPIDJMS-61:
{quote}
it would be nice to be able to preconfigure sasl mechanisms such that the sasl init could be sent before the other end sends the supported mechanisms. This greatly reduces the amount of work a proxy must do but does bypass negotiation
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org