[
https://issues.apache.org/jira/browse/QPID-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620669#comment-14620669
]
Rob Godfrey commented on QPID-6633:
-----------------------------------
Hi Nathan,
>From he error above it seems like the .net client is trying to authenticate
>using PLAIN (i.e. sending the username and password in cleartext). By default
>the Qpid Broker no longer allows PLAIN authentication over non-TLS enabled
>connections as a security measure. The mail here:
>http://mail-archives.apache.org/mod_mbox/qpid-users/201506.mbox/%[email protected]%3E
> explains how you can enable PLAIN on a non-TLS port.
Alternatively if you are not actually looking for any sort of meaningful
authentication of the connection, you could switch to use anonymous
authentication on your AMQP port.
> JAVA QPID Broker 0.30 - internal-error: Sasl error: no common mechanism
> -----------------------------------------------------------------------
>
> Key: QPID-6633
> URL: https://issues.apache.org/jira/browse/QPID-6633
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30
> Environment: Windows 8 64 Bit
> Reporter: Nathan Lusher
> Priority: Blocker
>
> I am trying to test some code against version 0.30 of the JAVA QPID broker
> but I am unable to connect to it. The code works against the 0.28 JAVA broker
> and the 0.32 CPP broker. The code is part of a .NET application which
> references the Org.Apache.Qpid.Messaging.dll. Here is the code:
> ...
> using Org.Apache.Qpid.Messaging;
> ...
> Connection = new Connection("localhost:5672", "{username:guest,
> password:guest}");
> Connection.Open();
> The following exception is thrown on the second line:
> *internal-error: Sasl error: no common mechanism*
> Does anyone have any idea what may be causing this issue?
> Thanks in advance,
> Nathan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
