But we can already do such rules - in probably a more efficient manner,
as target is simpler to evaluate
GRANT
resource match: (string-equal "/foo" resource_ancestors)
condition: (string-match "*.html" resource-id)
Or maybe you can setup your system to use
Resource match: (Boolean-equal "true" is_static_page_flag)
:)
Why more complexity, especially with functions used in target
matching...
Daniel..
-----Original Message-----
From: Rich Salz [mailto:]
Sent: Wednesday, June 16, 2004 4:10 PM
To: Tim Moses
Cc: 'Michiharu Kudoh'; 'xacml'
Subject: RE: [xacml] URI match function
> url-branch-match?
how about subtree instead of branch? might be possible to have
/foo/**/*.html
match all static web pages, e.g.
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview
http://www.datapower.com/xmldev/xmlsecurity.html
To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgro
up.php.
