----- Original Message ----- > From: "Ganesh Murthy" <gmur...@redhat.com> > To: users@qpid.apache.org > Sent: Friday, March 10, 2017 3:18:04 PM > Subject: Re: [Qpid Proton] How mandatory is Cyrus for SASL > > > > ----- Original Message ----- > > From: "Alan Conway" <acon...@redhat.com> > > To: users@qpid.apache.org > > Sent: Tuesday, February 7, 2017 2:56:20 PM > > Subject: Re: [Qpid Proton] How mandatory is Cyrus for SASL > > > > On Tue, 2017-02-07 at 19:32 +0100, Rabih M wrote: > > > Hello, > > > > > > I compiled qpid-proton 0.16.0 with "-DSASL_IMPL=none", but i have an > > > 3 of qpid-dispatch 0.7.0 unit tests that are failing: > > > > > > system_tests_qdstat > > > system_tests_sasl_plain > > > system_tests_deprecated > > > > > > I attached the tests output. > > > > > > Do you have any idea, where should i look? Is Cyrus mandatory for the > > > qpid-dispatch 0.7.0? > > > > Not mandatory, the tests should probably be made conditional to skip > > tests for SASL features that are not available. Raise a JIRA for that. > > > > Is there a way for dispatch to find out if proton is using the none sasl > implementation ("-DSASL_IMPL=none") so it can skip certain tests? > Looks like bool pn_sasl_extended(void) returns true in cyrus_sasl.c and false in none_sasl.c, so I can use that.
Thanks. > > > Best regards, > > > Rabih > > > > > > On Thu, Feb 2, 2017 at 10:18 PM, Andrew Stitcher <astitc...@redhat.co > > > m> wrote: > > > > On Thu, 2017-02-02 at 19:54 +0000, Adel Boutros wrote: > > > > > In our case, we only use EXTERNAL or ANONYMOUS so it should be > > > > > enough. > > > > > > > > > > > > > > > Is there a reason it is called "null"? > > > > > > > > It's actually the "none" implementation! As in, no other sasl > > > > library > > > > found. > > > > > > > > You can make sure it is used by adding "-DSASL_IMPL=none" to the > > > > cmake > > > > command line. Or use ccmake to set SASL_IMPL interactively. > > > > > > > > Andrew > > > > > > > > > > > > ----------------------------------------------------------------- > > > > ---- > > > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org