Service bus authenticates to the link ("entity"), so it is perfectly normal
to have connection and session operations succeed with bogus credentials
followed by a link attach failure.However, I can't say that you actually have an authentication issue since you have success with at least one of the test programs you have created. Perhaps running the client with environment variable PN_TRACE_FRM=1 set to see what Proton is actually sending and receiving? On Monday, 18 July 2016, Tobias Duckworth <tob...@duckworth.uk.com> wrote: > OK, so I managed to fire up a local broker that requires SSL and everything > works fine... I can open sessions, senders, receivers, send a message etc. > > So it seems that the problem is specific to Azure, although not sure why it > works with the non connection_engine build, but not with the > connection_engine. I'm guessing there's something I'm not doing in relation > to SSL setup that Azure requires, but have not yet found what it is. Also > find it a little strange that the connection can be opened, sessions > opened, > but things fall apart when links are opened. > > Anyway, seems not to be a fundamental problem with using libcurl to deal > with all the SSL side of things, which is good. > > Toby > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/qpid-proton-0-12-2-connection-engine-and-ssl-tp7647090p7647803.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org <javascript:;> > For additional commands, e-mail: users-h...@qpid.apache.org <javascript:;> > >
