delta/python-packages/qpid-python.git/qpid/cpp/src/tests/sasl_fed_ex, branch help

QPID-3152

2011-03-18T02:44:42+00:00

The non-clustered versions of the sasl_fed_ex tests should probably not attempt to load cluster.so.  


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

QPID-1672

2011-03-08T20:59:26+00:00

clustered versions of the 4 federated sasl external tests.


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

QPID-1672

2011-03-07T11:22:19+00:00

The core script sasl_fed_ex ( used by sasl_fed_ex_* ) is modified to 
encapsulate broker creation, and handle clustering -- toggled by a new 
argument.  
This is an intermediate checkin.  There are not yet any scripts that 
actually invoke the new clustering capability.


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

What was a single test -- sasl_fed_ex -- is now

2011-02-28T18:00:10+00:00

4 tests with a common core.  They are:

  sasl_fed_ex_dynamic
  sasl_fed_ex_link
  sasl_fed_ex_queue
  sasl_fed_ex_route 

( and the common core is sasl_fed_ex )

These tests correspond to the 4 different ways that the 
qpid-route command has of making links, or links+routes.
All those pathways have to be modified so that the new
"mechanism" argument information can be passed down and
used -- so that you can specify a SASL mechnism to be
used on the interbroker link that you create.

( So -- the qpid-route command also had to be modified
to propagate the mechanism info with all 4 subcommands. )

Since the SASL mechanism is owned by the link, these 
tests check that the link comes up and becomes operational.

Finally, I modified the sasl-mechanism flag in qpid-route
to call it "client-sasl-mechanism" to better distinguish 
between the SASL mechanism used in the created route -- and
the SASL mechanism (if any) that is used when the qpid-route 
client itself connects to the broker that it is talking to.



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

Remove unnecessary sleeps.

2011-01-11T17:29:22+00:00

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

config.null line wasn't needed, and was messing up vpath builds.

2011-01-06T19:21:38+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1056019 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

In broker::ConectionHandler, use the security settings, if any,

2010-12-16T21:10:38+00:00

provided by the transport layer when starting SASL.
This allows the SASL mechanism EXTERNAL to be satisfied with 
SSL transport security.
The test, sasl_fed_ex, uses this SASL/SSL security on a 
federated link between two brokers.


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