[
https://issues.apache.org/jira/browse/ARTEMIS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363378#comment-15363378
]
ASF GitHub Bot commented on ARTEMIS-578:
----------------------------------------
Github user jbertram commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/622#discussion_r69647599
--- Diff:
artemis-protocols/artemis-stomp-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/stomp/v11/StompFrameHandlerV11.java
---
@@ -16,6 +16,7 @@
*/
package org.apache.activemq.artemis.core.protocol.stomp.v11;
+import javax.security.cert.X509Certificate;
--- End diff --
This was implemented on core via
https://issues.apache.org/jira/browse/ARTEMIS-261. This PR is just for Stomp. I
believe other protocols will need to be examined on an individual basis.
> Enable certificate-based authn and authz for STOMP
> --------------------------------------------------
>
> 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)
