delta/python-packages/qpid-python.git/qpid/cpp/src/tests/sasl_fed, branch 0.14

QPID-3150

2011-03-17T20:45:55+00:00

This is a test-only fix.
Tell the client explicitly to use DIGEST-MD5, rather than possibly defaulting to a mech that the test has not prepared for.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1082685 13f79535-47bb-0310-9956-ffa450edef68

Change tmp directories from /tmp/sasl_fed/RANDOM to /tmp/sasl_fed_RANDOM.

2010-12-17T21:09:20+00:00

Otherwise, if user A runs these tests first, user B can't come along and
run them later -- if he doesn't have write permission to the /tmp/sasl_fed 
directory which user A already created.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1050493 13f79535-47bb-0310-9956-ffa450edef68

Remove spurious comment.

2010-11-02T19:08:01+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1030180 13f79535-47bb-0310-9956-ffa450edef68

Prevent sasl_fed from blowing up in a distro, or "make distcheck",

2010-10-29T18:51:11+00:00

by bailing out if the python tools that it needs are absent.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1028878 13f79535-47bb-0310-9956-ffa450edef68

Clarify this output comment a little.

2010-10-28T10:31:22+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1028250 13f79535-47bb-0310-9956-ffa450edef68

Add a small executable that prints out the sasl version number in integer form.

2010-10-28T04:39:43+00:00

Use it in the sasl_fed test to determine whether that test can run.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1028180 13f79535-47bb-0310-9956-ffa450edef68

This code's purpose was only to print out the sasl version into the logs

2010-10-26T15:25:40+00:00

so that I could grep for it in the sasl_fed test.  But it is breaking the
windows build.   So I am backing it out, and temporarily disabling the 
sasl_fed test until I can implement something a little less grotesque.



git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1027594 13f79535-47bb-0310-9956-ffa450edef68

Changes to make it work in vpath build!

2010-10-25T19:37:26+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1027243 13f79535-47bb-0310-9956-ffa450edef68

Fix this test to parse the sasl version number out of the new logging statement printed by broker #2 -- and exit if the version number is too low to support redirection of the sasl database file.

2010-10-22T07:57:35+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1026233 13f79535-47bb-0310-9956-ffa450edef68

SASLizing Interbroker Links

2010-10-20T08:03:36+00:00

-------------------------------------------------------------

1. Brokers already knew how to handle the server side of SASLized
links, but not the client side. So we promoted the client-side
SASL code from the client library to the common library so that
the broker could also use it. This affected SaslFactory.{h,cpp}
and Sasl.h
TODO -- can the server-side and client-side code be unified here?

2. Some of the SASL verbs in broker/ConnectionHandler.cpp are
expanded: start, secure, tune.

3. broker/SecureConnection is altered to get the client-broker and
the server-broker to agree on when the security layer should be
inserted.

4. the python tool qpid-route is modified so that, in the "route add"
command, you can specify the security mechanism for SASL to use.
TODO -- should we also pass in {min,max}SSF ?

5. Changes in broker/LinkRegistry to allow the information input by
qpid-route to be passed up to where it is needed.

6. A bash script test run by "make check" that creates a SASLized
federation link and sends some messages down it.
TODO - write a python unit test instead of a bash script. I
think I uncovered a bug in the python code when I tried.

7. NOTE - testing for this feature does not work with versions of
SASL earlier than 2.1.22, becuase I can't tell SASL to use a
SASL database file in a nonstandard location. The test is
disabled for earlier versions.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1024541 13f79535-47bb-0310-9956-ffa450edef68