RE: [xacml] Proposed PAP Architecture

[Hal Lockhart <hal.lockhart@oracle.com>]

This is another example of functionality I would expect to be in many environments, but like source code control, I did not see it as an essential element. Further, there are many products in this space and they might be integrated with the rest of the PAP architecture in one of several ways. That said, if the TC feels this should be in the architecture, I am quite willing to add it.

Hal

> -----Original Message-----
> From: Danny Thorpe [mailto:Danny.Thorpe@quest.com]
> Sent: Thursday, June 14, 2012 1:14 PM
> To: Hal Lockhart; xacml@lists.oasis-open.org
> Subject: RE: [xacml] Proposed PAP Architecture
> 
> This document calls out Policy testing and analysis as a separate
> function, presumably a prerequisite to deployment of a changed policy.
> However, there is no mention of a corresponding administrative review
> and change approval process - the notion that before a policy change
> entered by a policy administrator can be deployed, the change must be
> reviewed and approved by another person of sufficient seniority in the
> organization.
> 
> Is this notion of administrative change approval workflow appropriate
> to include in the PAP architecture diagram?
> 
> -Danny
> 
> Danny Thorpe
> Product Architect | | Quest Software - Now including the people and
> products of BiTKOO | www.quest.com
> 
> > -----Original Message-----
> > From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org]
> > On Behalf Of Hal Lockhart
> > Sent: Tuesday, June 12, 2012 3:31 PM
> > To: xacml@lists.oasis-open.org
> > Subject: [xacml] Proposed PAP Architecture
> >
> > I have added a new page to the wiki to develop an agreed upon minimum
> > architecture for the sub components of the Policy Administration
> Point
> > (PAP).
> >
> > https://wiki.oasis-
> > open.org/xacml/Policy%20Administration%20Point%20Architecture
> >
> > I believe that if we can come to agreement on these components and
> > their functions, it will provide a solid basis for defining the
> > necessary protocols and interfaces.
> >
> > Please take a look and make comments or modifications.
> >
> > Hal
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: xacml-help@lists.oasis-open.org
>