You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2016/02/03 22:19:39 UTC
[jira] [Created] (DISPATCH-213) Qpid dispatch management tools need
explanation of hidden SASL conventions
Chuck Rolke created DISPATCH-213:
------------------------------------
Summary: Qpid dispatch management tools need explanation of hidden SASL conventions
Key: DISPATCH-213
URL: https://issues.apache.org/jira/browse/DISPATCH-213
Project: Qpid Dispatch
Issue Type: Improvement
Reporter: Chuck Rolke
Tool users would benefit a lot from a few comments that are the commit for DISPATCH-116 making their way into the to tool --help text. Namely:
{noformat}
NOTE: If --ssl options are present the tools will automatically assume the
amqps: scheme for the URL.
NOTE: --sasl-mechanism option was removed. Presently proton only supports
ANONYMOUS and PLAIN and will auto-detect the SASL mechanism from the URL as
follows:
amqp://host - no SASL at all
amqp://anonymous@host - ANONYMOUS mechanism
amqp://user:password@host - PLAIN mechanism
The tools will add anonymous@ if no user is present to force the use of SASL as this
is most compatible with dispatch. Dispatch can allow no-SASL connections but requires
explicit configuration, and SASL connections will always work.
Additional SASL support is in progress, we will update the tools when it is clear how
additional mechanisms are specified.
{noformat}
--
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