qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jonat...@apache.org
Subject svn commit: r1066676 [1/8] - in /qpid/site/docs/books/trunk: AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/ AMQP-Messaging-Broker-Java-Book/html/ AMQP-Messaging-Broker-Java-Book/pdf/ Programming-In-Apache-Qpid/html/ Programmin...
Date Wed, 02 Feb 2011 22:58:38 GMT
Author: jonathan
Date: Wed Feb  2 22:58:35 2011
New Revision: 1066676

URL: http://svn.apache.org/viewvc?rev=1066676&view=rev
Log:
Updated C++ Broker and Programming in Apache Qpid to latest source.

Modified:
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s03.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s04.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s05.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s07.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/index.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/pr01.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/pdf/AMQP-Messaging-Broker-CPP-Book.pdf
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch01.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch01s02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch01s03.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch01s04.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch01s05.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s03.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s04.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s05.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s06.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s07.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s08.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s09.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s10.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch02s11.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch03.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04s02.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pt01.html
    qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch01.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s02.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s03.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s04.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s08.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s09.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s10.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s11.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s12.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s13.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s14.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s15.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s16.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s02.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s04.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s05.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s02.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s03.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html
    qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/pdf/Programming-In-Apache-Qpid.pdf

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html Wed Feb  2 22:58:35 2011
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1.  Running the AMQP Messaging Broker</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="prev" href="pr01.html" title="Introduction"><link rel="next" href="ch01s02.html" title="1.2.  Cheat Sheet for configuring Queue Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1.  Running the AMQP Messaging Broker</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="prev" href="pr01.html" title="Introduction"><link rel="next" href="ch01s02.html" title="1.2.  Cheat Sheet for configuring Queue Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 1.  Running the AMQP Messaging Broker"><div class="titlepage"><div><div><h2 class="title"><a name="id2649104"></a>Chapter 1.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch01s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 1.  Running the AMQP Messaging Broker"><div class="titlepage"><div><div><h2 class="title"><a name="id2709180"></a>Chapter 1. 
       Running the AMQP Messaging Broker
     </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch01.html#section-Running-a-Qpid-CPP-Broker">1.1. 
     Running a Qpid C++ Broker
@@ -28,11 +28,7 @@
     Cheat Sheet for configuring Exchange Options
   </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s03.html#CheatSheetforconfiguringExchangeOptions-ConfiguringExchangeOptions">1.3.1. 
       Configuring Exchange Options
-    </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s04.html">1.4. Broker Federation</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Message_Routes">1.4.1. Message Routes</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Federation_Topologies">1.4.2. Federation Topologies</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Federation_among_High_Availability_Message_Clusters">1.4.3. Federation among High Availability Message Clusters</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-The_qpid_route_Utility">1.4.4. The qpid-route Utility</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s05.html">1.5. 
-      SSL
-    </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s05.html#SSL-SSLHowto">1.5.1. 
-            SSL How to
-          </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s06.html">1.6. 
+    </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s04.html">1.4. Broker Federation</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Message_Routes">1.4.1. Message Routes</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Federation_Topologies">1.4.2. Federation Topologies</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-Federation_among_High_Availability_Message_Clusters">1.4.3. Federation among High Availability Message Clusters</a></span></dt><dt><span class="section"><a href="ch01s04.html#sect-Messaging_User_Guide-Broker_Federation-The_qpid_route_Utility">1.4.4. The qpid-route Utility</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s05.html">1.5. Security</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s05.html#sect-Messaging_User_Guide-Security-U
 ser_Authentication">1.5.1. User Authentication</a></span></dt><dt><span class="section"><a href="ch01s05.html#sect-Messaging_User_Guide-Security-Authorization">1.5.2. Authorization</a></span></dt><dt><span class="section"><a href="ch01s05.html#sect-Messaging_User_Guide-Security-Encryption_using_SSL">1.5.3. Encryption using SSL</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s06.html">1.6. 
       LVQ
     </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s06.html#LVQ-UnderstandingLVQ">1.6.1. 
             Understanding LVQ
@@ -49,22 +45,14 @@
       Asynchronous
       Replication of Queue State
     </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s08.html">1.8. High Availability Messaging Clusters</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s08.html#sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Starting_a_Broker_in_a_Cluster">1.8.1. Starting a Broker in a Cluster</a></span></dt><dt><span class="section"><a href="ch01s08.html#sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-qpid_cluster">1.8.2. qpid-cluster</a></span></dt><dt><span class="section"><a href="ch01s08.html#sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Failover_in_Clients">1.8.3. Failover in Clients</a></span></dt><dt><span class="section"><a href="ch01s08.html#sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Error_handling_in_Clusters">1.8.4. Error handling in Clusters</a></span></dt><dt><span class="section"><a href="ch01s08.html#sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Persistence_in_H
 igh_Availability_Message_Clusters">1.8.5. Persistence in High Availability Message Clusters</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s09.html">1.9. 
-      ACL
-  </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s09.html#ACL-v2ACLfileformatforbrokers">1.9.1. 
-      v2 ACL file format for brokers
-    </a></span></dt><dt><span class="section"><a href="ch01s09.html#ACL-DesignDocumentation">1.9.2. 
-            Design Documentation
-          </a></span></dt><dt><span class="section"><a href="ch01s09.html#ACL-v2ACLUserGuide">1.9.3. 
-            v2 ACL User Guide
-          </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s10.html">1.10. 
       AMQP compatibility
-    </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s10.html#AMQPcompatibility-AMQPCompatibilityofQpidreleases-3A">1.10.1. 
+    </a></span></dt><dd><dl><dt><span class="section"><a href="ch01s09.html#AMQPcompatibility-AMQPCompatibilityofQpidreleases-3A">1.9.1. 
             AMQP
             Compatibility of Qpid releases:
-          </a></span></dt><dt><span class="section"><a href="ch01s10.html#AMQPcompatibility-InteroptablebyAMQPspecificationversion">1.10.2. 
+          </a></span></dt><dt><span class="section"><a href="ch01s09.html#AMQPcompatibility-InteroptablebyAMQPspecificationversion">1.9.2. 
             Interop
             table by AMQP specification version
-          </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s11.html">1.11. Qpid Interoperability Documentation</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s11.html#QpidInteroperabilityDocumentation-SASL">1.11.1. 
+          </a></span></dt></dl></dd><dt><span class="section"><a href="ch01s10.html">1.10. Qpid Interoperability Documentation</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s10.html#QpidInteroperabilityDocumentation-SASL">1.10.1. 
             SASL
           </a></span></dt></dl></dd></dl></div><div class="section" title="1.1.  Running a Qpid C++ Broker"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-Running-a-Qpid-CPP-Broker"></a>1.1. 
     Running a Qpid C++ Broker

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s02.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s02.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.2.  Cheat Sheet for configuring Queue Options</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="next" href="ch01s03.html" title="1.3.  Cheat Sheet for configuring Exchange Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.2. 
       Cheat Sheet for configuring Queue Options
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr></table><hr></div><div class="section" title="1.2.  Cheat Sheet for configuring Queue Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579600"></a>1.2. 
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr></table><hr></div><div class="section" title="1.2.  Cheat Sheet for configuring Queue Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2709085"></a>1.2. 
       Cheat Sheet for configuring Queue Options
     </h2></div></div></div><div class="section" title="1.2.1.  Configuring Queue Options"><div class="titlepage"><div><div><h3 class="title"><a name="CheatSheetforconfiguringQueueOptions-ConfiguringQueueOptions"></a>1.2.1. 
             Configuring
@@ -188,7 +188,7 @@
             Note that these options can be set from any client. QueueOptions
             just correctly formats the arguments passed to the QueueDeclare()
             method.
-          </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1.             
+          </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. 
       Running the AMQP Messaging Broker
      </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.3. 
     Cheat Sheet for configuring Exchange Options

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s03.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s03.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.3.  Cheat Sheet for configuring Exchange Options</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s02.html" title="1.2.  Cheat Sheet for configuring Queue Options"><link rel="next" href="ch01s04.html" title="1.4. Broker Federation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.3. 
     Cheat Sheet for configuring Exchange Options
-  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr></table><hr></div><div class="section" title="1.3.  Cheat Sheet for configuring Exchange Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648511"></a>1.3. 
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr></table><hr></div><div class="section" title="1.3.  Cheat Sheet for configuring Exchange Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2709035"></a>1.3. 
     Cheat Sheet for configuring Exchange Options
   </h2></div></div></div><div class="section" title="1.3.1.  Configuring Exchange Options"><div class="titlepage"><div><div><h3 class="title"><a name="CheatSheetforconfiguringExchangeOptions-ConfiguringExchangeOptions"></a>1.3.1. 
       Configuring Exchange Options

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s04.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s04.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s04.html Wed Feb  2 22:58:35 2011
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.4. Broker Federation</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s03.html" title="1.3.  Cheat Sheet for configuring Exchange Options"><link rel="next" href="ch01s05.html" title="1.5.  SSL"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.4. Broker Federation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.4. Broker Federation</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s03.html" title="1.3.  Cheat Sheet for configuring Exchange Options"><link rel="next" href="ch01s05.html" title="1.5. Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.4. Broker Federation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
     </th><td width="20%" align="right"> <a accesskey="n" href="ch01s05.html">Next</a></td></tr></table><hr></div><div class="section" title="1.4. Broker Federation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap-Messaging_User_Guide-Broker_Federation"></a>1.4. Broker Federation</h2></div></div></div><p>
 		<em class="firstterm">Broker Federation</em> allows messaging networks to be defined by creating <em class="firstterm">message routes</em>, in which messages in one broker (the <em class="firstterm">source broker</em>) are automatically routed to another broker (the <em class="firstterm">destination broker</em>). These routes may be defined between exchanges in the two brokers (the <em class="firstterm">source exchange</em> and the <em class="firstterm">destination exchange</em>), or from a queue in the source broker (the <em class="firstterm">source queue</em>) to an exchange in the destination broker. Message routes are unidirectional; when bidirectional flow is needed, one route is created in each direction. Routes can be durable or transient. A durable route survives broker restarts, restoring a route as soon as both the source broker and the destination are available. If the connection to a destination is lost, messages associated with a durable route continue to accu
 mulate on the source, so they can be retrieved when the connection is reestablished.
@@ -317,6 +317,4 @@ localhost       10009   tcp          N  
 								If a cluster is federated to another cluster, only one of the nodes has an actual connection to remote node. Other nodes in the cluster have a passive connection.
 							</td></tr></tbody></table></div></div><br class="table-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.3. 
     Cheat Sheet for configuring Exchange Options
-   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.5. 
-      SSL
-    </td></tr></table></div></body></html>
+   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.5. Security</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s05.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s05.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s05.html Wed Feb  2 22:58:35 2011
@@ -1,100 +1,531 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.5.  SSL</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s04.html" title="1.4. Broker Federation"><link rel="next" href="ch01s06.html" title="1.6.  LVQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.5. 
-      SSL
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.5. Security</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s04.html" title="1.4. Broker Federation"><link rel="next" href="ch01s06.html" title="1.6.  LVQ"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.5. Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s06.html">Next</a></td></tr></table><hr></div><div class="section" title="1.5.  SSL"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2649614"></a>1.5. 
-      SSL
-    </h2></div></div></div><div class="section" title="1.5.1.  SSL How to"><div class="titlepage"><div><div><h3 class="title"><a name="SSL-SSLHowto"></a>1.5.1. 
-            SSL How to
-          </h3></div></div></div><div class="section" title="1.5.1.1.  C++ broker (M4 and up)"><div class="titlepage"><div><div><h4 class="title"><a name="SSL-C-5Cbroker-28M4andup-29"></a>1.5.1.1. 
-            C++ broker (M4 and up)
-          </h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>You need to get a certificate signed by a CA, trusted by your
-            client.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>If you require client authentication, the clients certificate
-            needs to be signed by a CA trusted by the broker.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Setting up the certificates for testing.
-              </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>For testing purposes you could use the <a class="xref" href="">???</a> to setup your certificates.
-                </p></li><li class="listitem"><p>In summary you need to create a root CA and import it to
-                the brokers certificate data base.
-                </p></li><li class="listitem"><p>Create a certificate for the broker, sign it using the
-                root CA and then import it into the brokers certificate data
-                base.
-                </p></li></ul></div><p>
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Load the acl module using --load-module or if loading more
-            than one module, copy ssl.so to the location pointed by
-            --module-dir
-              
-                </p><pre class="programlisting">
-Ex if running from source. ./qpidd --load-module /libs/ssl.so
-</pre><p>
-              
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Specify the password file (a plain text file with the
-            password), certificate database and the brokers certificate name
-            using the following options
-              
-                </p><pre class="programlisting">
-Ex ./qpidd ... --ssl-cert-password-file ~/pfile --ssl-cert-db ~/server_db/ --ssl-cert-name localhost.localdomain
-</pre><p>
-              
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>If you require client authentication you need to add
-            --ssl-require-client-authentication as a command line argument.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Please note that the default port for SSL connections is
-            5671, unless specified by --ssl-port
-            </p></li></ul></div><p>
-            Here is an example of a broker instance that requires SSL client
-            side authenticaiton
-          </p><pre class="programlisting">
-./qpidd ./qpidd --load-module /libs/ssl.so --ssl-cert-password-file ~/pfile --ssl-cert-db ~/server_db/ --ssl-cert-name localhost.localdomain --ssl-require-client-authentication
-</pre></div><div class="section" title="1.5.1.2.  Java Client (M4 and up)"><div class="titlepage"><div><div><h4 class="title"><a name="SSL-JavaClient-28M4andup-29"></a>1.5.1.2. 
-            Java Client (M4 and up)
-          </h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>This guide is for connecting with the Qpid c++ broker.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Setting up the certificates for testing. In summary,
-              </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>You need to import the trusted CA in your trust store and
-                keystore
-                </p></li><li class="listitem"><p>Generate keys for the certificate in your key store
-                </p></li><li class="listitem"><p>Create a certificate request using the generated keys
-                </p></li><li class="listitem"><p>Create a certficate using the request, signed by the
-                trusted CA.
-                </p></li><li class="listitem"><p>Import the signed certificate into your keystore.
-                </p></li></ul></div><p>
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Pass the following JVM arguments to your client.
-              
-                </p><pre class="programlisting">
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s06.html">Next</a></td></tr></table><hr></div><div class="section" title="1.5. Security"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap-Messaging_User_Guide-Security"></a>1.5. Security</h2></div></div></div><p>
+		This chapter describes how authentication, rule-based authorization, encryption, and digital signing can be accomplished using Qpid. Authentication is the process of verifying the identity of a user; in Qpid, this is done using the SASL framework. Rule-based authorization is a mechanism for specifying the actions that each user is allowed to perform; in Qpid, this is done using an Access Control List (ACL) that is part of the Qpid broker. Encryption is used to ensure that data is not transferred in a plain-text format that could be intercepted and read. Digital signatures provide proof that a given message was sent by a known sender. Encryption and signing are done using SSL (they can also be done using SASL, but SSL provides stronger encryption).
+	</p><div class="section" title="1.5.1. User Authentication"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-Security-User_Authentication"></a>1.5.1. User Authentication</h3></div></div></div><p>
+			AMQP uses Simple Authentication and Security Layer (SASL) to authenticate client connections to the broker. SASL is a framework that supports a variety of authentication methods. For secure applications, we suggest <span class="command"><strong>CRAM-MD5</strong></span>, <span class="command"><strong>DIGEST-MD5</strong></span>, or <span class="command"><strong>GSSAPI</strong></span>. The <span class="command"><strong>ANONYMOUS</strong></span> method is not secure. The <span class="command"><strong>PLAIN</strong></span> method is secure only when used together with SSL.
+		</p><p>
+			Both the Qpid broker and Qpid clients use the <a class="ulink" href="http://cyrusimap.web.cmu.edu/" target="_top">Cyrus SASL library</a>, a full-featured authentication framework, which offers many configuration options. This section shows how to configure users for authentication with SASL, which is sufficient when using <span class="command"><strong>SASL PLAIN</strong></span>. If you are not using SSL, you should configure SASL to use <span class="command"><strong>CRAM-MD5</strong></span>, <span class="command"><strong>DIGEST-MD5</strong></span>, or <span class="command"><strong>GSSAPI</strong></span> (which provides Kerberos authentication). For information on configuring these and other options in SASL, see the Cyrus SASL documentation.
+		</p><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
+				The <span class="command"><strong>SASL PLAIN</strong></span> method sends passwords in cleartext, and is vulnerable to man-in-the-middle attacks unless SSL (Secure Socket Layer) is also used (see <a class="xref" href="ch01s05.html#sect-Messaging_User_Guide-Security-Encryption_using_SSL" title="1.5.3. Encryption using SSL">Section 1.5.3, &#8220;Encryption using SSL&#8221;</a>).
+			</p><p>
+				If you are not using SSL, we recommend that you disable <span class="command"><strong>PLAIN</strong></span> authentication in the broker.
+			</p></div><p>
+			The Qpid broker uses the <span class="command"><strong>auth yes|no</strong></span> option to determine whether to use SASL authentication. Turn on authentication by setting <span class="command"><strong>auth</strong></span> to <span class="command"><strong>yes</strong></span> in <code class="filename">/etc/qpidd.conf</code>:
+		</p><pre class="programlisting">
+# /etc/qpidd.conf
+#
+# Set auth to 'yes' or 'no'
+
+auth=yes
+</pre><div class="section" title="1.5.1.1. Configuring SASL"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-User_Authentication-Configuring_SASL"></a>1.5.1.1. Configuring SASL</h4></div></div></div><p>
+				On Linux systems, the SASL configuration file is generally found in <code class="filename">/etc/sasl2/qpidd.conf</code> or <code class="filename">/usr/lib/sasl2/qpidd.conf</code>.
+			</p><p>
+				The SASL database contains user names and passwords for SASL. In SASL, a user may be associated with a <em class="firstterm">realm</em>. The Qpid broker authenticates users in the <span class="command"><strong>QPID</strong></span> realm by default, but it can be set to a different realm using the <span class="command"><strong>realm</strong></span> option:
+			</p><pre class="programlisting">
+# /etc/qpidd.conf
+#
+# Set the SASL realm using 'realm='
+
+auth=yes
+realm=QPID
+</pre><p>
+				The SASL database is installed at <code class="filename">/var/lib/qpidd/qpidd.sasldb</code>; initially, it has one user named <span class="command"><strong>guest</strong></span> in the <span class="command"><strong>QPID</strong></span> realm, and the password for this user is <span class="command"><strong>guest</strong></span>.
+			</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+					The user database is readable only by the <code class="systemitem">qpidd</code> user. When run as a daemon, Qpid always runs as the <code class="systemitem">qpidd</code> user. If you start the broker from a user other than the <code class="systemitem">qpidd</code> user, you will need to either reconfigure SASL or turn authentication off.
+				</p></div><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
+					The SASL database stores user names and passwords in plain text. If it is compromised so are all of the passwords that it stores. This is the reason that the <code class="systemitem">qpidd</code> user is the only user that can read the database. If you modify permissions, be careful not to expose the SASL database.
+				</p></div><p>
+				Add new users to the database by using the <span class="command"><strong>saslpasswd2</strong></span> command, which specifies a realm and a user ID. A user ID takes the form <span class="command"><strong><em class="replaceable"><code>user-id</code></em>@<em class="replaceable"><code>domain</code></em>.</strong></span>.
+			</p><pre class="screen"># saslpasswd2 -f /var/lib/qpidd/qpidd.sasldb -u <em class="replaceable"><code>realm</code></em> <em class="replaceable"><code>new_user_name</code></em></pre><p>
+				To list the users in the SASL database, use <span class="command"><strong>sasldblistusers2</strong></span>:
+			</p><pre class="screen"># sasldblistusers2 -f /var/lib/qpidd/qpidd.sasldb
+</pre><p>
+				If you are using <span class="command"><strong>PLAIN</strong></span> authentication, users who are in the database can now connect with their user name and password. This is secure only if you are using SSL. If you are using a more secure form of authentication, please consult your SASL documentation for information on configuring the options you need.
+			</p></div><div class="section" title="1.5.1.2. Kerberos"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-User_Authentication-Kerberos"></a>1.5.1.2. Kerberos</h4></div></div></div><p>
+				Both the Qpid broker and Qpid users are 'principals' of the Kerberos server, which means that they are both clients of the Kerberos authentication services.
+			</p><p>
+				To use Kerberos, both the Qpid broker and each Qpid user must be authenticated on the Kerberos server:
+			</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
+						Install the Kerberos workstation software and Cyrus SASL GSSAPI on each machine that runs a qpidd broker or a qpidd messaging client:
+					</p><pre class="screen">$ sudo yum install cyrus-sasl-gssapi krb5-workstation</pre></li><li class="step" title="Step 2"><p>
+						Make sure that the Qpid broker is registered in the Kerberos database.
+					</p><p>
+						Traditionally, a Kerberos principal is divided into three parts: the primary, the instance, and the realm. A typical Kerberos V5 has the format <code class="literal">primary/instance@REALM</code>. For a Qpid broker, the primary is <code class="literal">qpidd</code>, the instance is the fully qualified domain name, which you can obtain using <span class="command"><strong>hostname --fqdn</strong></span>, and the REALM is the Kerberos domain realm. By default, this realm is <code class="literal">QPID</code>, but a different realm can be specified in qpid.conf, e.g.:
+</p><pre class="screen">realm=EXAMPLE.COM</pre><p>
+
+					</p><p>
+						For instance, if the fully qualified domain name is <code class="literal">dublduck.example.com</code> and the Kerberos domain realm is <code class="literal">EXAMPLE.COM</code>, then the principal name is <code class="literal">qpidd/dublduck.example.com@EXAMPLE.COM</code>.
+					</p><p>
+						The following script creates a principal for qpidd:
+					</p><pre class="programlisting">
+FDQN=`hostname --fqdn`
+REALM="EXAMPLE.COM"
+kadmin -r $REALM  -q "addprinc -randkey -clearpolicy qpidd/$FQDN"
+</pre><p>
+						Now create a Kerberos keytab file for the Qpid broker. The Qpid broker must have read access to the keytab file. The following script creates a keytab file and allows the broker read access:
+					</p><pre class="programlisting">
+QPIDD_GROUP="qpidd"
+kadmin -r $REALM  -q "ktadd -k /etc/qpidd.keytab qpidd/$FQDN@$REALM"
+chmod g+r /etc/qpidd.keytab
+chgrp $QPIDD_GROUP /etc/qpidd.keytab
+</pre><p>
+						The default location for the keytab file is <code class="filename">/etc/krb5.keytab</code>. If a different keytab file is used, the KRB5_KTNAME environment variable must contain the name of the file, e.g.:
+					</p><pre class="programlisting">
+export KRB5_KTNAME=/etc/qpidd.keytab
+</pre><p>
+						If this is correctly configured, you can now enable kerberos support on the Qpid broker by setting the <code class="varname">auth</code> and <code class="varname">realm</code> options in <code class="filename">/etc/qpidd.conf</code>:
+					</p><pre class="programlisting">
+# /etc/qpidd.conf
+auth=yes
+realm=EXAMPLE.COM
+</pre><p>
+						Restart the broker to activate these settings.
+					</p></li><li class="step" title="Step 3"><p>
+						Make sure that each Qpid user is registered in the Kerberos database, and that Kerberos is correctly configured on the client machine. The Qpid user is the account from which a Qpid messaging client is run. If it is correctly configured, the following command should succeed:
+					</p><pre class="screen">$ kinit user@REALM.COM</pre></li></ol></div><p>
+				Java JMS clients require a few additional steps.
+			</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
+						The Java JVM must be run with the following arguments:
+					</p><div class="variablelist"><dl><dt><span class="term">-Djavax.security.auth.useSubjectCredsOnly=false</span></dt><dd><p>
+									Forces the SASL GASSPI client to obtain the kerberos credentials explicitly instead of obtaining from the "subject" that owns the current thread.
+								</p></dd><dt><span class="term">-Djava.security.auth.login.config=myjas.conf</span></dt><dd><p>
+									Specifies the jass configuration file. Here is a sample JASS configuration file:
+								</p><pre class="programlisting">
+com.sun.security.jgss.initiate {
+    com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;
+};
+</pre></dd><dt><span class="term">-Dsun.security.krb5.debug=true</span></dt><dd><p>
+									Enables detailed debug info for troubleshooting
+								</p></dd></dl></div></li><li class="step" title="Step 2"><p>
+						The client's Connection URL must specify the following Kerberos-specific broker properties:
+					</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+								<code class="varname">sasl_mechs</code> must be set to <code class="literal">GSSAPI</code>.
+							</p></li><li class="listitem"><p>
+								<code class="varname">sasl_protocol</code> must be set to the principal for the qpidd broker, e.g. <code class="literal">qpidd</code>/
+							</p></li><li class="listitem"><p>
+								<code class="varname">sasl_server</code> must be set to the host for the SASL server, e.g. <code class="literal">sasl.com</code>.
+							</p></li></ul></div><p>
+						Here is a sample connection URL for a Kerberos connection:
+					</p><pre class="screen">amqp://guest@clientid/testpath?brokerlist='tcp://localhost:5672?sasl_mechs='GSSAPI'&amp;sasl_protocol='qpidd'&amp;sasl_server='&lt;server-host-name&gt;''</pre></li></ol></div></div></div><div class="section" title="1.5.2. Authorization"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-Security-Authorization"></a>1.5.2. Authorization</h3></div></div></div><p>
+			In Qpid, Authorization specifies which actions can be performed by each authenticated user using an Access Control List (ACL). Use the <span class="command"><strong>--acl-file</strong></span> command to load the access control list. The filename should have a <code class="filename">.acl</code> extension:
+		</p><pre class="screen">
+$ qpidd --acl-file <em class="replaceable"><code>./aclfilename.acl</code></em></pre><p>
+			Each line in an ACL file grants or denies specific rights to a user. If the last line in an ACL file is <code class="literal">acl deny all all</code>, the ACL uses <em class="firstterm">deny mode</em>, and only those rights that are explicitly allowed are granted:
+		</p><pre class="programlisting">
+acl allow rajith@QPID all all
+acl deny all all
+</pre><p>
+			On this server, <code class="literal">rajith@QPID</code> can perform any action, but nobody else can. Deny mode is the default, so the previous example is equivalent to the following ACL file:
+		</p><pre class="programlisting">
+acl allow rajith@QPID all all
+</pre><p>
+			In deny mode, denying rights to an action is redundant and has no effect.
+		</p><pre class="programlisting">
+acl allow rajith@QPID all all
+acl deny jonathan@QPID all all # This rule is redundant, and has no effect
+acl deny all all
+</pre><p>
+			If the last line in an ACL file is <code class="literal">acl allow all all</code>, ACL uses <em class="firstterm">allow mode</em>, and all rights are granted except those that are explicitly denied. The following ACL file allows everyone else to perform any action, but denies <code class="literal">jonathan@QPID</code> all permissions.
+		</p><pre class="programlisting">
+acl deny jonathan@QPID all all
+acl allow all all
+</pre><p>
+			In allow mode, allowing rights to an action is redundant and has no effect.
+		</p><pre class="programlisting">
+acl allow rajith@QPID all all # This rule is redundant, and has no effect
+acl deny jonathan@QPID all all
+acl allow all all
+</pre><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
+				ACL processing ends when one of the following lines is encountered:
+			</p><pre class="programlisting">
+acl allow all all
+</pre><pre class="programlisting">
+acl deny all all
+</pre><p>
+				Any lines that occur after one of these statements will be ignored:
+			</p><pre class="programlisting">
+acl allow all all
+acl deny jonathan@QPID all all # This line is ignored !!!
+</pre></div><p>
+			ACL syntax allows fine-grained access rights for specific actions:
+		</p><pre class="programlisting">
+acl allow carlt@QPID create exchange name=carl.*
+acl allow fred@QPID create all
+acl allow all consume queue
+acl allow all bind exchange
+acl deny all all
+</pre><p>
+			An ACL file can define user groups, and assign permissions to them:
+		</p><pre class="programlisting">
+group admin ted@QPID martin@QPID
+acl allow admin create all
+acl deny all all
+</pre><div class="section" title="1.5.2.1. ACL Syntax"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Authorization-ACL_Syntax"></a>1.5.2.1. ACL Syntax</h4></div></div></div><p>
+				ACL rules must be on a single line and follow this syntax:
+</p><pre class="programlisting">acl permission {&lt;group-name&gt;|&lt;user-name&gt;|"all"} {action|"all"} [object|"all"] [property=&lt;property-value&gt;]
+</pre><p>
+				 ACL rules can also include a single object name (or the keyword <em class="parameter"><code>all</code></em>) and one or more property name value pairs in the form <span class="command"><strong>property=value</strong></span>
+			</p><p>
+				The following tables show the possible values for <span class="command"><strong>permission</strong></span>, <span class="command"><strong>action</strong></span>, <span class="command"><strong>object</strong></span>, and <span class="command"><strong>property</strong></span> in an ACL rules file.
+			</p><div class="table"><a name="tabl-Messaging_User_Guide-ACL_Syntax-ACL_Rules_permission"></a><p class="title"><b>Table 1.3. ACL Rules: permission</b></p><div class="table-contents"><table summary="ACL Rules: permission" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+								<span class="command"><strong>allow</strong></span>
+							</td><td>
+								<p>
+									Allow the action 
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>allow-log</strong></span>
+							</td><td>
+								<p>
+									Allow the action and log the action in the event log
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>deny</strong></span>
+							</td><td>
+								<p>
+									Deny the action
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>deny-log</strong></span>
+							</td><td>
+								<p>
+									Deny the action and log the action in the event log
+								</p>
+
+							</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="tabl-Messaging_User_Guide-ACL_Syntax-ACL_Rulesaction"></a><p class="title"><b>Table 1.4. ACL Rules:action</b></p><div class="table-contents"><table summary="ACL Rules:action" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+								<span class="command"><strong>consume</strong></span>
+							</td><td>
+								<p>
+									Applied when subscriptions are created
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>publish</strong></span>
+							</td><td>
+								<p>
+									Applied on a per message basis on publish message transfers, this rule consumes the most resources
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>create</strong></span>
+							</td><td>
+								<p>
+									Applied when an object is created, such as bindings, queues, exchanges, links
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>access</strong></span>
+							</td><td>
+								<p>
+									Applied when an object is read or accessed
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>bind</strong></span>
+							</td><td>
+								<p>
+									Applied when objects are bound together
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>unbind</strong></span>
+							</td><td>
+								<p>
+									Applied when objects are unbound
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>delete</strong></span>
+							</td><td>
+								<p>
+									Applied when objects are deleted
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>purge</strong></span>
+							</td><td>
+								<p>
+									Similar to delete but the action is performed on more than one object
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>update</strong></span>
+							</td><td>
+								<p>
+									Applied when an object is updated
+								</p>
+
+							</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="tabl-Messaging_User_Guide-ACL_Syntax-ACL_Rulesobject"></a><p class="title"><b>Table 1.5. ACL Rules:object</b></p><div class="table-contents"><table summary="ACL Rules:object" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+								<span class="command"><strong>queue</strong></span>
+							</td><td>
+								<p>
+									A queue
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>exchange</strong></span>
+							</td><td>
+								<p>
+									An exchange
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>broker</strong></span>
+							</td><td>
+								<p>
+									The broker
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>link</strong></span>
+							</td><td>
+								<p>
+									A federation or inter-broker link
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>method</strong></span>
+							</td><td>
+								<p>
+									Management or agent or broker method
+								</p>
+
+							</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="tabl-Messaging_User_Guide-ACL_Syntax-ACL_Rulesproperty"></a><p class="title"><b>Table 1.6. ACL Rules:property</b></p><div class="table-contents"><table summary="ACL Rules:property" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+								<span class="command"><strong>name</strong></span>
+							</td><td>
+								<p>
+									String. Object name, such as a queue name or exchange name.
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>durable</strong></span>
+							</td><td>
+								<p>
+									Boolean. Indicates the object is durable
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>routingkey</strong></span>
+							</td><td>
+								<p>
+									Sring. Specifies routing key
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>passive</strong></span>
+							</td><td>
+								<p>
+									Boolean. Indicates the presence of a <em class="parameter"><code>passive</code></em> flag
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>autodelete</strong></span>
+							</td><td>
+								<p>
+									Boolean. Indicates whether or not the object gets deleted when the connection is closed
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>exclusive</strong></span>
+							</td><td>
+								<p>
+									Boolean. Indicates the presence of an <em class="parameter"><code>exclusive</code></em> flag
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>type</strong></span>
+							</td><td>
+								<p>
+									String. Type of object, such as topic, fanout, or xml
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>alternate</strong></span>
+							</td><td>
+								<p>
+									String. Name of the alternate exchange
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>queuename</strong></span>
+							</td><td>
+								<p>
+									String. Name of the queue (used only when the object is something other than <em class="parameter"><code>queue</code></em>
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>schemapackage</strong></span>
+							</td><td>
+								<p>
+									String. QMF schema package name
+								</p>
+
+							</td></tr><tr><td>
+								<span class="command"><strong>schemaclass</strong></span>
+							</td><td>
+								<p>
+									String. QMF schema class name
+								</p>
+
+							</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="1.5.2.2. ACL Syntactic Conventions"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Authorization-ACL_Syntactic_Conventions"></a>1.5.2.2. ACL Syntactic Conventions</h4></div></div></div><p>
+				In ACL files, the following syntactic conventions apply:
+				</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+							A line starting with the <span class="command"><strong>#</strong></span> character is considered a comment and is ignored.
+						</p></li><li class="listitem"><p>
+							Empty lines and lines that contain only whitespace are ignored
+						</p></li><li class="listitem"><p>
+							All tokens are case sensitive. <em class="parameter"><code>name1</code></em> is not the same as <em class="parameter"><code>Name1</code></em> and <em class="parameter"><code>create</code></em> is not the same as <em class="parameter"><code>CREATE</code></em>
+						</p></li><li class="listitem"><p>
+							Group lists can be extended to the following line by terminating the line with the <span class="command"><strong>\</strong></span> character
+						</p></li><li class="listitem"><p>
+							Additional whitespace - that is, where there is more than one whitespace character - between and after tokens is ignored. Group and ACL definitions must start with either <span class="command"><strong>group</strong></span> or <span class="command"><strong>acl</strong></span> and with no preceding whitespace.
+						</p></li><li class="listitem"><p>
+							All ACL rules are limited to a single line
+						</p></li><li class="listitem"><p>
+							Rules are interpreted from the top of the file down until the name match is obtained; at which point processing stops.
+						</p></li><li class="listitem"><p>
+							The keyword <em class="parameter"><code>all</code></em> matches all individuals, groups and actions
+						</p></li><li class="listitem"><p>
+							The last line of the file - whether present or not - will be assumed to be <span class="command"><strong>acl deny all all</strong></span>. If present in the file, all lines below it are ignored.
+						</p></li><li class="listitem"><p>
+							Names and group names may contain only <em class="parameter"><code>a-z</code></em>, <em class="parameter"><code>A-Z</code></em>, <em class="parameter"><code>0-9</code></em>, <em class="parameter"><code>-</code></em> and <em class="parameter"><code>_</code></em>
+						</p></li><li class="listitem"><p>
+							Rules must be preceded by any group definitions they can use. Any name not defined as a group will be assumed to be that of an individual.
+						</p></li></ul></div><p>
+
+			</p></div><div class="section" title="1.5.2.3. Specifying ACL Permissions"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Authorization-Specifying_ACL_Permissions"></a>1.5.2.3. Specifying ACL Permissions</h4></div></div></div><p>
+				Now that we have seen the ACL syntax, we will provide representative examples and guidelines for ACL files.
+			</p><p>
+				Most ACL files begin by defining groups:
+			</p><pre class="programlisting">
+group admin ted@QPID martin@QPID
+group user-consume martin@QPID ted@QPID
+group group2 kim@QPID user-consume rob@QPID
+group publisher group2 \
+tom@QPID andrew@QPID debbie@QPID
+</pre><p>
+				Rules in an ACL file grant or deny specific permissions to users or groups:
+			</p><pre class="programlisting">
+acl allow carlt@QPID create exchange name=carl.*
+acl allow rob@QPID create queue
+acl allow guest@QPID bind exchange name=amq.topic routingkey=stocks.rht.#
+acl allow user-consume create queue name=tmp.*
+
+acl allow publisher publish all durable=false
+acl allow publisher create queue name=RequestQueue
+acl allow consumer consume queue durable=true
+acl allow fred@QPID create all
+acl allow bob@QPID all queue
+acl allow admin all
+acl allow all consume queue
+acl allow all bind exchange
+acl deny all all
+</pre><p>
+				In the previous example, the last line, <code class="literal">acl deny all all</code>, denies all authorizations that have not been specifically granted. This is the default, but it is useful to include it explicitly on the last line for the sake of clarity. If you want to grant all rights by default, you can specify <code class="literal">acl allow all all</code> in the last line.
+			</p><p>
+				Do not allow <em class="parameter"><code>guest</code></em> to access and log QMF management methods that could cause security breaches:
+			</p><pre class="programlisting">
+group allUsers guest@QPID
+....
+acl deny-log allUsers create link
+acl deny-log allUsers access method name=connect
+acl deny-log allUsers access method name=echo
+acl allow all all
+</pre></div></div><div class="section" title="1.5.3. Encryption using SSL"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-Security-Encryption_using_SSL"></a>1.5.3. Encryption using SSL</h3></div></div></div><p>
+			Encryption and certificate management for <span class="command"><strong>qpidd</strong></span> is provided by Mozilla's Network Security Services Library (NSS).
+		</p><div class="orderedlist" title="Enabling SSL for the Qpid broker"><a name="orde-Messaging_User_Guide-Encryption_using_SSL-Enabling_SSL_for_the_RHM_broker"></a><p class="title"><b>Enabling SSL for the Qpid broker</b></p><ol class="orderedlist" type="1"><li class="listitem"><p>
+					You will need a certificate that has been signed by a Certification Authority (CA). This certificate will also need to be trusted by your client. If you require client authentication in addition to server authentication, the client's certificate will also need to be signed by a CA and trusted by the broker.
+				</p><p>
+					In the broker, SSL is provided through the <span class="command"><strong>ssl.so</strong></span> module. This module is installed and loaded by default in Qpid. To enable the module, you need to specify the location of the database containing the certificate and key to use. This is done using the <span class="command"><strong>ssl-cert-db</strong></span> option.
+				</p><p>
+					The certificate database is created and managed by the Mozilla Network Security Services (NSS) <span class="command"><strong>certutil</strong></span> tool. Information on this utility can be found on the <a class="ulink" href="http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html" target="_top">Mozilla website</a>, including tutorials on setting up and testing SSL connections. The certificate database will generally be password protected. The safest way to specify the password is to place it in a protected file, use the password file when creating the database, and specify the password file with the <span class="command"><strong>ssl-cert-password-file</strong></span> option when starting the broker.
+				</p><p>
+					The following script shows how to create a certificate database using certutil:
+				</p><pre class="programlisting">
+mkdir ${CERT_DIR}
+certutil -N -d ${CERT_DIR} -f ${CERT_PW_FILE}
+certutil -S -d ${CERT_DIR} -n ${NICKNAME} -s "CN=${NICKNAME}" -t "CT,," -x -f ${CERT_PW_FILE} -z /usr/bin/certutil
+</pre><p>
+					When starting the broker, set <span class="command"><strong>ssl-cert-password-file</strong></span> to the value of <span class="command"><strong>${CERT_PW_FILE}</strong></span>, set <span class="command"><strong>ssl-cert-db</strong></span> to the value of <span class="command"><strong>${CERT_DIR}</strong></span>, and set <span class="command"><strong>ssl-cert-name</strong></span> to the value of <span class="command"><strong>${NICKNAME}</strong></span>.
+				</p></li><li class="listitem"><p>
+					The following SSL options can be used when starting the broker:
+					</p><div class="variablelist"><dl><dt><span class="term"><span class="command"><strong>--ssl-use-export-policy</strong></span></span></dt><dd><p>
+									Use NSS export policy
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-cert-password-file <em class="replaceable"><code>PATH</code></em></strong></span></span></dt><dd><p>
+									Required. Plain-text file containing password to use for accessing certificate database.
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-cert-db <em class="replaceable"><code>PATH</code></em></strong></span></span></dt><dd><p>
+									Required. Path to directory containing certificate database.
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-cert-name <em class="replaceable"><code>NAME</code></em></strong></span></span></dt><dd><p>
+									Name of the certificate to use. Default is <code class="literal">localhost.localdomain</code>.
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-port <em class="replaceable"><code>NUMBER</code></em></strong></span></span></dt><dd><p>
+									Port on which to listen for SSL connections. If no port is specified, port 5671 is used.
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-require-client-authentication</strong></span></span></dt><dd><p>
+									Require SSL client authentication (i.e. verification of a client certificate) during the SSL handshake. This occurs before SASL authentication, and is independent of SASL.
+								</p><p>
+									This option enables the <code class="literal">EXTERNAL</code> SASL mechanism for SSL connections. If the client chooses the <code class="literal">EXTERNAL</code> mechanism, the client's identity is taken from the validated SSL certificate, using the <code class="literal">CN</code>literal&gt;, and appending any <code class="literal">DC</code>literal&gt;s to create the domain. For instance, if the certificate contains the properties <code class="literal">CN=bob</code>, <code class="literal">DC=acme</code>, <code class="literal">DC=com</code>, the client's identity is <code class="literal">bob@acme.com</code>.
+								</p><p>
+									If the client chooses a different SASL mechanism, the identity take from the client certificate will be replaced by that negotiated during the SASL handshake.
+								</p></dd><dt><span class="term"><span class="command"><strong>--ssl-sasl-no-dict</strong></span></span></dt><dd><p>
+									Do not accept SASL mechanisms that can be compromised by dictionary attacks. This prevents a weaker mechanism being selected instead of <code class="literal">EXTERNAL</code>, which is not vulnerable to dictionary attacks.
+								</p></dd></dl></div><p>
+					 Also relevant is the <span class="command"><strong>--require-encryption</strong></span> broker option. This will cause <span class="command"><strong>qpidd</strong></span> to only accept encrypted connections.
+				</p></li></ol></div><div class="variablelist" title="Enabling SSL in Clients"><a name="vari-Messaging_User_Guide-Encryption_using_SSL-Enabling_SSL_in_Clients"></a><p class="title"><b>Enabling SSL in Clients</b></p><dl><dt><span class="term">C++ clients:</span></dt><dd><p>
+						</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+									In C++ clients, SSL is implemented in the <span class="command"><strong>sslconnector.so</strong></span> module. This module is installed and loaded by default in Qpid.
+								</p><p>
+									The following options can be specified for C++ clients using environment variables:
+								</p><div class="table"><a name="tabl-Messaging_User_Guide-Enabling_SSL_in_Clients-SSL_Client_Environment_Variables_for_C_clients"></a><p class="title"><b>Table 1.7. SSL Client Environment Variables for C++ clients</b></p><div class="table-contents"><table summary="SSL Client Environment Variables for C++ clients" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
+													SSL Client Options for C++ clients
+												</th></tr></thead><tbody><tr><td align="left">
+													<span class="command"><strong>QPID_SSL_USE_EXPORT_POLICY</strong></span>
+												</td><td align="left">
+													Use NSS export policy
+												</td></tr><tr><td align="left">
+													<span class="command"><strong>QPID_SSL_CERT_PASSWORD_FILE <em class="replaceable"><code>PATH</code></em></strong></span>
+												</td><td align="left">
+													File containing password to use for accessing certificate database
+												</td></tr><tr><td align="left">
+													<span class="command"><strong>QPID_SSL_CERT_DB <em class="replaceable"><code>PATH</code></em></strong></span>
+												</td><td align="left">
+													Path to directory containing certificate database
+												</td></tr><tr><td align="left">
+													<span class="command"><strong>QPID_SSL_CERT_NAME <em class="replaceable"><code>NAME</code></em></strong></span>
+												</td><td align="left">
+													Name of the certificate to use. When SSL client authentication is enabled, a certificate name should normally be provided.
+												</td></tr></tbody></table></div></div><br class="table-break"></li><li class="listitem"><p>
+									When using SSL connections, clients must specify the location of the certificate database, a directory that contains the client's certificate and the public key of the Certificate Authority. This can be done by setting the environment variable <span class="command"><strong>QPID_SSL_CERT_DB</strong></span> to the full pathname of the directory. If a connection uses SSL client authentication, the client's password is also needed&#8212;the password should be placed in a protected file, and the <span class="command"><strong>QPID_SSL_CERT_PASSWORD_FILE</strong></span> variable should be set to the location of the file containing this password.
+								</p></li><li class="listitem"><p>
+									To open an SSL enabled connection in the Qpid Messaging API, set the <em class="parameter"><code>protocol</code></em> connection option to <em class="parameter"><code>ssl</code></em>.
+								</p></li></ol></div><p>
+
+					</p></dd><dt><span class="term">Java clients:</span></dt><dd><p>
+						</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+									For both server and client authentication, import the trusted CA to your trust store and keystore and generate keys for them. Create a certificate request using the generated keys and then create a certificate using the request. You can then import the signed certificate into your keystore. Pass the following arguments to the Java JVM when starting your client:
+</p><pre class="programlisting">
 -Djavax.net.ssl.keyStore=/home/bob/ssl_test/keystore.jks
-   -Djavax.net.ssl.keyStorePassword=password
-   -Djavax.net.ssl.trustStore=/home/bob/ssl_test/certstore.jks
-   -Djavax.net.ssl.trustStorePassword=password
-</pre><p>
-              
-            </p></li></ul></div></div><div class="section" title="1.5.1.3.  .Net Client (M4 and up)"><div class="titlepage"><div><div><h4 class="title"><a name="SSL-.NetClient-28M4andup-29"></a>1.5.1.3. 
-            .Net Client (M4 and up)
-          </h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>If the Qpid broker requires client authentication then you
-            need to get a certificate signed by a CA, trusted by your client.
-            </p></li></ul></div><p>
-            Use the connectSSL instead of the standard connect method of the
-            client interface.
-          </p><p>
-            connectSSL signature is as follows:
-          </p><pre class="programlisting">
-public void connectSSL(String host, int port, String virtualHost, String username, String password, String serverName, String certPath, bool rejectUntrusted)
-</pre><p>
-            Where
-          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>host: Host name on which a Qpid broker is deployed
-            </p></li><li class="listitem"><p>port: Qpid broker port
-            </p></li><li class="listitem"><p>virtualHost: Qpid virtual host name
-            </p></li><li class="listitem"><p>username: User Name
-            </p></li><li class="listitem"><p>password: Password
-            </p></li><li class="listitem"><p>serverName: Name of the SSL server
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>certPath: Path to the X509 certificate to be used when the
-            broker requires client authentication
-            </p></li><li class="listitem"><p>rejectUntrusted: If true connection will not be established
-            if the broker is not trusted (the server certificate must be
-            added in your truststore)
-            </p></li></ul></div></div><div class="section" title="1.5.1.4.  Python &amp; Ruby Client (M4 and up)"><div class="titlepage"><div><div><h4 class="title"><a name="SSL-Python-26RubyClient-28M4andup-29"></a>1.5.1.4. 
-            Python &amp;
-            Ruby Client (M4 and up)
-          </h4></div></div></div><p>
-            Simply use amqps:// in the URL string as defined above
-          </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.4. Broker Federation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.6. 
+-Djavax.net.ssl.keyStorePassword=password
+-Djavax.net.ssl.trustStore=/home/bob/ssl_test/certstore.jks
+-Djavax.net.ssl.trustStorePassword=password
+</pre><p>
+
+								</p></li><li class="listitem"><p>
+									For server side authentication only, import the trusted CA to your trust store and pass the following arguments to the Java JVM when starting your client:
+</p><pre class="programlisting">
+-Djavax.net.ssl.trustStore=/home/bob/ssl_test/certstore.jks
+-Djavax.net.ssl.trustStorePassword=password
+</pre><p>
+
+								</p></li><li class="listitem"><p>
+									Java clients must use the SSL option in the connection URL to enable SSL encryption, e.g.
+								</p><pre class="programlisting">amqp://username:password@clientid/test?brokerlist='tcp://localhost:5672?ssl='true''
+</pre></li><li class="listitem"><p>
+									If you need to debug problems in an SSL connection, enable Java's SSL debugging by passing the argument <code class="literal">-Djavax.net.debug=ssl</code> to the Java JVM when starting your client.
+								</p></li></ol></div><p>
+
+					</p></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.4. Broker Federation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.6. 
       LVQ
     </td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.6.  LVQ</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s05.html" title="1.5.  SSL"><link rel="next" href="ch01s07.html" title="1.7.  Queue State Replication"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.6. 
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.6.  LVQ</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s05.html" title="1.5. Security"><link rel="next" href="ch01s07.html" title="1.7.  Queue State Replication"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.6. 
       LVQ
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s05.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s05.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s07.html">Next</a></td></tr></table><hr></div><div class="section" title="1.6.  LVQ"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2649424"></a>1.6. 
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s07.html">Next</a></td></tr></table><hr></div><div class="section" title="1.6.  LVQ"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2716699"></a>1.6. 
       LVQ
     </h2></div></div></div><div class="section" title="1.6.1.  Understanding LVQ"><div class="titlepage"><div><div><h3 class="title"><a name="LVQ-UnderstandingLVQ"></a>1.6.1. 
             Understanding LVQ
@@ -319,8 +319,6 @@ int main(int argc, char** argv) 
     return 1;
 }
 
-</pre></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s07.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.5. 
-      SSL
-     </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.7. 
+</pre></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s07.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.5. Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.7. 
     Queue State Replication
   </td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s07.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s07.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s07.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s07.html Wed Feb  2 22:58:35 2011
@@ -1,6 +1,6 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.7.  Queue State Replication</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s06.html" title="1.6.  LVQ"><link rel="next" href="ch01s08.html" title="1.8. High Availability Messaging Clusters"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.7. 
     Queue State Replication
-  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s06.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s06.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
     </th><td width="20%" align="right"> <a accesskey="n" href="ch01s08.html">Next</a></td></tr></table><hr></div><div class="section" title="1.7.  Queue State Replication"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="queue-state-replication"></a>1.7. 
     Queue State Replication



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message