[
https://issues.apache.org/jira/browse/ARTEMIS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341208#comment-15341208
]
Lionel Cons commented on ARTEMIS-578:
-------------------------------------
I forgot to add: I have only tested STOMP which is configured via:
{code}
<acceptor
name="stomp+ssl">tcp://0.0.0.0:6023?protocols=STOMP;enabledProtocols=TLSv1,TLSv1.1,TLSv1.2;keyStorePassword=xxx;keyStorePath=/.../broker.ks;needClientAuth=true;sslEnabled=true;trustStorePassword=xxx;trustStorePath=/.../broker.ts</acceptor>
{code}
> X.509 authentication does not seem to work
> ------------------------------------------
>
> Key: ARTEMIS-578
> URL: https://issues.apache.org/jira/browse/ARTEMIS-578
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Lionel Cons
> Assignee: Justin Bertram
>
> This is a follow up of ARTEMIS-529.
> Using the newly added dual authentication, my test program fails to
> authenticate. I get:
> {code}
> 2016-06-20 09:19:40,563
> [org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager]
> INFO Couldn't validate user: user name is null
> {code}
> The same program (with the exact same credentials) works fine against an
> ActiveMQ 5.x broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
