[
https://issues.apache.org/jira/browse/ARTEMIS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341203#comment-15341203
]
Lionel Cons commented on ARTEMIS-578:
-------------------------------------
I have tried with the latest snapshot (1.4.0-20160621.030808-9) and with
"single authentication" as per:
{code}
<jaas-security domain="CertificateLogin"/>
{code}
and
{code}
CertificateLogin {
org.apache.activemq.artemis.spi.core.security.jaas.TextFileCertificateLoginModule
required
debug=true
reload=true
org.apache.activemq.jaas.textfiledn.user="dns.properties"
org.apache.activemq.jaas.textfiledn.role="groups.properties";
};
{code}
The broker does not log anything (no {{INFO}}, no {{WARN}}) and the client gets
an {{ERROR}} frame with "Security Error occurred: User name [null] or password
is invalid".
So, this does not seem to be linked with dual authentication (hence
ARTEMIS-529).
> 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)
