This is a re-send of the original message with the particulars updated
for the new location of the SASL wrapper. By popular demand, this
wrapper was moved out of the qpid/cpp area and moved to qpid/extras.
=================================================================
Full SASL authentication/encryption capability for the Python client was
added to the trunk at revision 835550.
A new Python module "saslwrapper" implemented in C++ and wrapped for Python
using Swig was introduced. This wrapper provides a generalized binding
to the Cyrus SASL library. The Python client tries to import this
module. If it cannot find it, it will revert to built-in capability
that only provides ANONYMOUS and PLAIN authentication mechanisms.
To build this module, you need the python-devel and swig packages. From
the directory qpid/extras/sasl, type the commands:
$ ./bootstrap
$ ./configure
$ make
To use it, your PYTHONPATH must provide access to the following files
(or these files need to be copied to where the PYTHONPATH can reach them):
$(build_dir)/python/saslwrapper.py
$(build_dir)/python/.libs/_saslwrapper.so
The following library is also built (it contains the C++ implemented
SASL wrapper):
$(build_dir)/src/.libs/libsaslwrapper.so
When creating the Connection object, you may supply the "mechanism"
argument with a space-separated list of acceptable authentication
mechanisms. If this argument is left to the default value of None
(recommended), the SASL library will pick the best available mechanism
for you.
For Kerberos5 single-sign-on, the GSSAPI mechanism is used.
Some notes/caveats:
This is not yet hooked into the newer qpid.messaging API.
This is not built under CMake yet.
This implementation is specific to Linux/Unix. It is possible that a
Windows implementation of the wrapper can be developed.
SASL EXTERNAL (i.e. use of SSL/TLS client certificates) is not yet
supported. This will be forthcoming.
Note also that I intend to add a Ruby binding to this module and move
the Ruby client to it. Ruby already has this capability but using the
same one that python uses will reduce future support headaches.
-Ted
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
