blob: c04d6e021c1c2ca2e49a93f33223d4d1b1b0e703 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
<html>
<head>
<title>Apache Qpid : Qpid Design - Access Control Lists</title>
<link rel="stylesheet" href="styles/site.css" type="text/css" />
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<table class="pagecontent" border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#ffffff">
<tr>
<td valign="top" class="pagebody">
<div class="pageheader">
<span class="pagetitle">
Apache Qpid : Qpid Design - Access Control Lists
</span>
</div>
<div class="pagesubheading">
This page last changed on Dec 06, 2007 by <font color="#0050B2">ritchiem</font>.
</div>
<h3><a name="QpidDesign-AccessControlLists-Overview"></a>Overview</h3>
<p>The AMQ Protocol specification has not yet formaly specified how access control lists should be specified or implemented as a result this is subject to change</p>
<p>The Java Qpid provides an authentication framework based on SASL, that provides the ability to plug in arbitrary user (or more strictly <em>principal</em>) databases and different SASL-compliant mechanisms. This mechanism has been extended as a proof of concept to allow access rights to a virtual host. What this page will present is an extension of this early work to include full access control across all objects in the system.</p>
<p>The current access file would be modified to provide additional objects for control:</p>
</td>
</tr>
</table>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td height="12" background="border/border_bottom.gif"><img src="border/spacer.gif" width="1" height="1" border="0"/></td>
</tr>
<tr>
<td align="center"><font color="grey">Document generated by Confluence on Apr 22, 2008 02:47</font></td>
</tr>
</table>
</body>
</html>
|
