xacml — archive

RE: [xacml] Minutes of 20 May 2004 XACML Focus Group

From: Anne Anderson <[email protected]>
To: [email protected]
Date: Fri, 21 May 2004 13:18:00 -0000

 MHonArc v2.5.0b2 -->

xacml message

[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]

Subject: RE: [xacml] Minutes of 20 May 2004 XACML Focus Group

From: Anne Anderson <[email protected]>
To: Daniel Engovatov <[email protected]>
Date: Fri, 21 May 2004 09:22:17 -0400

If you want to name your resources in a way other than the std
URI syntax, all you have to do is write a simple Profile
describing how your resources are named.  This could be an XACML
TC Profile or it could be a Profile used only by BEA for BEA
resources.

The important thing is for any given resource type to be
identified in only one way.  Otherwise, policies might be written
against the resource assuming one naming scheme, but the Request
might come in using another naming scheme, and then the policy
will not apply (when it should).

Anne

On 20 May, Daniel Engovatov writes: RE: [xacml] Minutes of 20 May 2004 XACML Focus Group
 > From: Daniel Engovatov <[email protected]>
 > To: [email protected]
 > Subject: RE: [xacml] Minutes of 20 May 2004 XACML Focus Group
 > Date: Thu, 20 May 2004 13:25:46 -0700
 > 
 > ..Or did I misunderstood something? :)
 > Sorry.
 > 
 > Just my use case does not fit well into any standardized hierarchical
 > name
 > Syntax (our naming authority in WLES giving our customers headaches - to
 > support old Crosslogix resource naming). 
 > 
 > I actually hooked up Sun's code as a test and it worked nicely with
 > "ancestors" approach.
 > 
 > Daniel.
 > 
 >