Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 209.85.198.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
        b=kC8ZUQZsb48itCKhaCgR4dCN5C2Pl52fEzejLq0R7F4bp8bTqV602+oMWoLEort47vHYncvNT2p2aSjkFheF3LVnx7AmgG86EWvMs1bCXjmw5GHsryUz4W40h7bIAdYFakkTf2DHJ3nFjUkAIU3L4E2kap20dzE2tkk6EJJkF/Q=
Message-ID: <a32f6b020710241014ya0c93baja47e96406f7eacc2@mail.gmail.com>
Date: Wed, 24 Oct 2007 13:14:05 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: [Triplesec] [AuthZ] Introduction
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9176_1593547.1193246045411"

------=_Part_9176_1593547.1193246045411
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Introduction
-----------------

This series describes the circumstances resulting in the need for a
centralized
authorization policy management system.  In doing so, it defines a subset of
the
problems that must be solved by Triplesec's Authorization Manager.  These
problems
and the various use cases described here resonate the goals of the Apache
Triplesec
Project with respect to authorization policy.

We're going to talk about applications, identities, permissions, roles,
groups, and the
assignment of roles to individual identities as well as to groups of
identities.  This will
lead us into discussions regarding what these entities are with clear
definitions we can
agree on and use as the nomenclature for this aspect of Triplesec.

Let us try to be as exacting as possible when speaking about these concepts
and
defining them eventually for use in a glossary section of our Triplesec
documentation.

Thanks,
Alex

------=_Part_9176_1593547.1193246045411
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Introduction<br>-----------------<br><br>This series describes the circumstances resulting in the need for a centralized<br>authorization policy management system.&nbsp; In doing so, it defines a subset of the <br>problems that must be solved by Triplesec&#39;s Authorization Manager.&nbsp; These problems
<br>and the various use cases described here resonate the goals of the Apache Triplesec <br>Project with respect to authorization policy.<br><br>We&#39;re going to talk about applications, identities, permissions, roles, groups, and the
<br>assignment of roles to individual identities as well as to groups of identities.&nbsp; This will <br>lead us into discussions regarding what these entities are with clear definitions we can<br>agree on and use as the nomenclature for this aspect of Triplesec.&nbsp; 
<br><br>Let us try to be as exacting as possible when speaking about these concepts and <br>defining them eventually for use in a glossary section of our Triplesec documentation.<br><br>Thanks,<br>Alex<br>

------=_Part_9176_1593547.1193246045411--