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

certificate-based authentication always fails for nio+ssl protocol

XMLWordPrintable

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

      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.

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

              Created:
              Updated:
              Resolved: