I tried to set following ...
pn_messenger_set_flags(messenger, PN_FLAGS_ALLOW_INSECURE_MECHS);
without any good result.
However in the pni_process_mechanisms function I see that if client receives
EXTERNAL from server in the SASL mechanisms list, this is the first to be used
even if I set the above flag.
Paolo.
Paolo PatiernoSenior Software Engineer
Windows Embedded & IoTMicrosoft Azure Insider
Twitter : @ppatierno
Linkedin : paolopatierno
Blog : DevExperienceBlog : Embedded101
To: users@qpid.apache.org
From: ppatie...@live.com
Subject: RE: SASL mechanism different between 0.9.1 and 0.10
Date: Tue, 1 Sep 2015 20:52:50 +0200
Yes Gordon ... You are right I'm speaking about messenger APIs
Sent from my Windows Phone
From:
Gordon Sim
Sent:
01/09/2015 20:39
To:
users@qpid.apache.org
Subject:
Re: SASL mechanism different between 0.9.1 and 0.10
On 09/01/2015 07:29 PM, Andrew Stitcher wrote:
> You may have to modify the send example
I suspect this is the send example using the messenger API. Is there a
way to control the mechanisms used with that API?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
