summaryrefslogtreecommitdiff
path: root/qpid
diff options
context:
space:
mode:
authorGordon Sim <gsim@apache.org>2010-03-05 17:56:23 +0000
committerGordon Sim <gsim@apache.org>2010-03-05 17:56:23 +0000
commit357fc1619a345ffaf0802f200f94cbba533267ef (patch)
tree39da0962aadededcace6546e062af72f5f491b22 /qpid
parent6b0a19d2d0d5ba68c0bc25aefb5931545ac572d7 (diff)
downloadqpid-python-357fc1619a345ffaf0802f200f94cbba533267ef.tar.gz
Updated SASL support grid
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@919520 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid')
-rw-r--r--qpid/doc/book/src/SASL-Compatibility.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/qpid/doc/book/src/SASL-Compatibility.xml b/qpid/doc/book/src/SASL-Compatibility.xml
index 96c523e519..beb138c182 100644
--- a/qpid/doc/book/src/SASL-Compatibility.xml
+++ b/qpid/doc/book/src/SASL-Compatibility.xml
@@ -12,18 +12,18 @@ This table list the various SASL mechanisms that each component supports. The ve
functionality was added to the product.
|| Component || ANONYMOUS || CRAM-MD5 || DIGEST-MD5 || EXTERNAL || GSSAPI/Kerberos || PLAIN ||
-| C++ Broker |M3\[[#1]\] |M3\[[#1],[#2]\]| | |M3\[[#1],[#2]\] | M1 |
-| C++ Client |M3\[[#1]\] | | | | | M1 |
+| C++ Broker |M3 |M3 | M3 |0.8\[[#1]\]|M3 | M1 |
+| C++ Client |M3 |0.5 | 0.5 |0.8\[[#1]\]| | M1 |
| Java Broker | | M1 | | | | M1 |
-| Java Client | | M1 | | | | M1 |
+| Java Client | | M1 | | M1 | | M1 |
| .Net Client | M2 | M2 | M2 | M2 | | M2 |
-| Python Client | | | | | | ? |
-| Ruby Client | | | | | | ? |
+| Python Client |0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4 |
+| Ruby Client |0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4 |
{anchor:1}
-1: Support for these will be in M3 (currently available on trunk).
+1: Only enabled for client authenticated SSL connections.
{anchor:2}
-2: C++ Broker uses [Cyrus Sasl|http://freshmeat.net/projects/cyrussasl/] which supports CRAM-MD5 and GSSAPI but these have not been tested yet
+2: On linux only via cyrus-sasl integration.
h4. Custom Mechanisms