You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/03/12 18:07:38 UTC
[jira] [Comment Edited] (ACTIVEMQ6-58) unable to authenticate with
an AMQP client using SASL
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358982#comment-14358982 ]
Robbie Gemmell edited comment on ACTIVEMQ6-58 at 3/12/15 5:06 PM:
------------------------------------------------------------------
This has been fixed by other changes made since raising the issue, resolving.
was (Author: gemmellr):
This shas been fixed by other changes made since raising the issue, resolving.
> unable to authenticate with an AMQP client using SASL
> -----------------------------------------------------
>
> Key: ACTIVEMQ6-58
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-58
> Project: Apache ActiveMQ 6
> Issue Type: Bug
> Affects Versions: 6.0.0
> Reporter: Robbie Gemmell
>
> After building the distribution, I have been unable to get AMQP client to the broker using SASL PLAIN with username and password "guest", which appears to be the default from looking in activemq-users.xml.
> I can see the SASL challenge proceed, and return an apparent failure to authenticate. I was able to connect to an older released version of the broker.
> I had to disable security to get connected at all, at which point the sasl negotation returns success, by adding this in activemq-configuration.xml:
> <security-enabled>false</security-enabled>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)