[DISPATCH-213] Qpid dispatch management tools need explanation of hidden SASL conventions

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Backlog
• Component/s: Tools
• Assignee: Unassigned
• Reporter: Charles E. Rolke
• Created: 03/Feb/16 21:19
• Updated: 02/Apr/21 10:21

Description

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:

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.

Issue Links

• is related to: DISPATCH-958 Lacking documentation on authorization, authentication and SSL.