Qpid
  1. Qpid
  2. QPID-3654

ANONYMOUS SASL mechanism does not work on Java client

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.14, 0.15
    • Fix Version/s: 0.14, 0.15
    • Component/s: Java Client
    • Labels:
      None

      Description

      A trivial program which just tries to make a Connection fails if it uses a connection URL like:
      amqp://anonymous:@client/test?brokerlist='tcp://localhost?sasl_mechs='ANONYMOUS''

      This forces the client to use ANONYMOUS.

      Program snippet:

      import javax.jms.Connection;
      import javax.jms.ConnectionFactory;

      ...

      ConnectionFactory connectionFactory = ...
      Connection connection = connectionFactory.createConnection();
      FAILS HERE ^^^

      With exception:
      org.apache.qpid.transport.ConnectionException: Client and broker have no SASL mechanisms in common. Broker allows : PLAIN DIGEST-MD5 ANONYMOUS LOGIN CRAM-MD5 Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN, PLAIN] Client restricted itself to : ANONYMOUS

      Notice that the client doesn't think it supports ANONYMOUS.

        Activity

          People

          • Assignee:
            Andrew Stitcher
            Reporter:
            Andrew Stitcher
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development