[
https://issues.apache.org/jira/browse/ARTEMIS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363342#comment-15363342
]
ASF GitHub Bot commented on ARTEMIS-578:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/622
ARTEMIS-578 cert authn/z for STOMP
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-578
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/622.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #622
----
commit e706fb899631a37e8bf7ef50fd7e6c76f9215eec
Author: jbertram <[email protected]>
Date: 2016-06-21T17:03:16Z
ARTEMIS-578 cert authn/z for STOMP
----
> 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)
