Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2088

certificate-based authentication always fails for nio+ssl protocol

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.3.x
    • JBoss A-MQ 6.3
    • broker, jaas
    • None

    Description

      Similar to ENTMQ-1154, client certificate authentication works in the following scenario:

      Broker A
    ...
    <jaasDualAuthenticationPlugin 
        configuration="activemq"
        sslConfiguration="CertLogin" />
    ...
    <transportConnector name="sslTransportConnector" uri="ssl://0.0.0.0:61618?needClientAuth=true&amp;wantClientAuth=true"/>

Broker B
    ...
    networkConnector uri="static://(ssl://localhost:61618)" name="myNetworkConnector" duplex="true" consumerTTL="2" messageTTL="100" dynamicOnly="false">
    ...

      But if you change the transport to nio+ssl, the network connector fails with the following message:

      INFO | Stopping vm://localhosta#0 because Failed with SecurityException: User name [null] or password is invalid.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQ-1154 Authentication based on SSL certificate fails for secure WebSockets transport wss://

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gtully@redhat.com Gary Tully
              rhn-support-shiggs Stephen Higgs
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: