On 15 March 2018 at 13:42, Alan Conway <[email protected]> wrote: > > > On Thu, Mar 15, 2018 at 9:28 AM, Baptiste Robert > <[email protected]> wrote: >> >> Hello everybody, >> >> I currently have an issue with the qpid-proton c++ implementation on >> windows. I can't connect to a Java broker with an authenticationproviders >> set to : PlainPasswordFile. >> >> I built the simple_send examples and I can send messages to the broker if >> authenticationproviders is set to Anonymous. As soon as I reactivate >> PlainPasswordFile then I do not have any exception and exit code is set to >> 1, no messages are sent, and Y is display in the console. > > > If you are using the SASL plain mechanism without TLS/SSL you also need to > set the connection_option sasl_allow_insecure_mechs(true)
Likewise, Broker-J won't offer the PLAIN SASL mechanism over a non-TLS port to a peer. If you don't want to use TLS, it can be overridden using instructions that talk about overriding secureOnlyMechanisms you'll find here: https://qpid.apache.org/releases/qpid-broker-j-7.0.2/book/Java-Broker-Security.html#Java-Broker-Security-Authentication-Providers > > By default, SASL will disallow mechanisms that send plain-text passwords > unless the connection is encrypted - even though you will see PLAIN listed > in the set of allowed mechanisms from the server, it will ignored by the > client. > > See the attached example which lets you play with SASL settings. Also a tip: > set PN_TRACE_FRM=1 in your environment to get more information about the > connection negotiation, including some SASL info. > >> >> Maybe I miss a dependency ? >> >> Baptiste > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
