Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-4133

Different behaviour with similar connectors with identical option, URI validation would be nice to have

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.7.0
    • 5.8.0
    • Transport
    • None

    Description

      Hello,

      we noticed an inconsistent behaviour of stomp+ssl and stomp+nio+ssl with same connector options.

      • stomp+ssl works with both transport.needClientAuth=true and needClientAuth=true options
      • stomp+nio+ssl works with transport.needClientAuth=true but not with needClientAuth=true
        In this last case it fails with a non-obvious exception:
        junit.framework.ComparisonFailure: java.lang.SecurityException: Unable to authenticate transport without SSL certificate.
                at org.apache.activemq.security.JaasCertificateAuthenticationBroker.addConnection(JaasCertificateAuthenticationBroker.java:74)
                at org.apache.activemq.security.JaasDualAuthenticationBroker.addConnection(JaasDualAuthenticationBroker.java:98)
        

      It would be nice to have a URI parameters validation or the same behaviour with similar connectors.

      What do you think?

      Unit test which shows the problem attached, sorry for reusing pieces from another bug.

      Attachments

        1. AMQ4133.tgz
          2 kB
          Massimo Paladin

        Activity

          People

            Unassigned Unassigned
            mpaladin Massimo Paladin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: