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:03:02 UTC
[jira] [Assigned] (QPIDJMS-69) add support for configuring allowed
SASL mechanism(s)
[ https://issues.apache.org/jira/browse/QPIDJMS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPIDJMS-69:
-------------------------------------
Assignee: Robbie Gemmell
> add support for configuring allowed SASL mechanism(s)
> -----------------------------------------------------
>
> Key: QPIDJMS-69
> URL: https://issues.apache.org/jira/browse/QPIDJMS-69
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
>
> The client supports a number of SASL mechanisms, from which it will select one based on the available credentials and supported server mechanisms (assuming there is a mutually supported usuable mechanism).
> It may be beneficical in some cases to configure/restrict the usuable mechanisms. In the case where only one option is configured it may also be useful to optionally support pipelining output of the SASL frames if that is possible (depending on the mechanism, obviously only works for some).
> 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