OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xacml] Policy Distribtion / PAP


If we can leverage existing standardized work, then that'd be great. Thanks for the link. Do let us know when the spec is public.


On Tue, Aug 27, 2013 at 12:38 PM, Herrmann, Jan <jan.herrmann@siemens.com> wrote:

Hi David, all,

I agree that the PAP interface and maybe the details of policy references should addressed.

During the last OGC testbed we developed a first version of a PAP WS specification and a corresponding PoC prototype. Currently all this staff is available for OGC members only (https://portal.opengeospatial.org/files/?artifact_id=54008). During the next OGC technical committee meeting in September this work will be voted on and (if it passes) made available for the public. I hope that you find a chance to read the first draft PAP WS specification and that we can somehow base our work on this document.

Best regards

Jan

 

Von: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org] Im Auftrag von David Brossard
Gesendet: Montag, 26. Au
gust 2013 15:25
An: Hill, Richard C
Cc: xacml@lists.oasis-open.org
Betreff: Re: [xacml] Policy Distribtion

 

Hi Richard, everyone,

 

In Ray's initial REST draft, he included a standardized PAP API. I believe this was axed later. I think we should revisit that effort.

 

Thoughts?

 

On Fri, Aug 23, 2013 at 8:06 PM, Hill, Richard C <Richard.C.Hill@boeing.com> wrote:

As I mentioned on yesterday's TC call, it's starting to be become apparent that large companies and multi-agency government entities will need a standard way to distribute XACML policies (e.g. sync updates from a centralized policy repository point to PDPs). The XACML 3.0 specification, section 2.9 Policy distribution, leaves policy distribution implementation to XACML product companies. Understandably, these implementations may be fine tuned to work well with one company's XACML products, but may not with another company's XACML products. Additionally, it cannot be guaranteed that each org in a large company or all government agencies will use the same company's XACML products. I believe that without a standard approach to distribute, sync, etc, XACML policies it may become a barrier to XACML adoption.

 

Hal Lockhart stated, on the TC call, that he has started work on trying to standardize this in the past and has taken the action to revive this effort. I would like to help with this and I encourage other to participate as well.

 

Hal, Is there a link on the Wiki on your past policy distribution work?

 

Thanks,

Richard



 

--
David Brossard, M.Eng, SCEA, CSTP
Product Manager
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden
http://www.linkedin.com/companies/536082
http://www.axiomatics.com
http://twitter.com/axiomatics




--
David Brossard, M.Eng, SCEA, CSTP
Product Manager
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden
http://www.linkedin.com/companies/536082
http://www.axiomatics.com
http://twitter.com/axiomatics


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]