Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-213

Qpid dispatch management tools need explanation of hidden SASL conventions

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • Backlog
    • Tools
    • None

    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.
      

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            chug Charles E. Rolke

            Dates

              Created:
              Updated:

              Slack

                Issue deployment