qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Restrepo" <tomas.restr...@devdeo.com>
Subject RE: Support SASL authentication in .NET client
Date Wed, 17 Jan 2007 11:18:16 GMT

> Hi Thomas, thanks for your patch for Qpid-291. I applied it and built and
> all looks good. Could you provide some brief instructions on how to test
> against a broker? Is there a config file or something I have to edit to
> up the policy etc.

Right now it's already working works against a broker and given the
configuration of the Java Broker at this time, CRAM-MD5 will be selected by
default as the authentication mechanism. Basically the client will
automatically select the mechanism based on what the server sends (i.e.
available mechanisms) and the set of mechanisms supported by the client
(CRAM-MD5 and PLAIN in that order of preference).

What's missing at this point (and it's something I'm trying to figure out
the best way to do) is a way to a) configure additional Sasl mechanisms (the
core sasl library I built does support this, but it's not exposed in a
configurable fashion yet) and b) configure a callback handler for your
mechanism (that supplies any data required by it to complete the
authentication, like username or password).

Both of these things are not significant issues in that the extensibility
hooks are there both in Qpid.Sasl and Qpid.Client already, it's just a
matter of making it available through a config file option, basically. I'm
hoping to get that done as well soon (I've just been a bit busy this past
couple of days).

If you want to test with a particular mechanism at this point, you'd need to
modify the set of supported algorithms in the CallbackHandlerRegistry.cs
file (for example, just putting PLAIN before CRAM-MD5 will make the client
choose to authenticate using PLAIN.)

I'll try to submit a new patch containing those fixes before the end of the
week, so that it can be used over the two previous patches I submitted. I
spent some time cleaning up the code yesterday and removed about 40 FxCop
warnings (there are still a few left, though), so it will be a good idea to
get a new patch anyway.

Tomas Restrepo

View raw message