<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
XACML Enforcement
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/dgradl">Dan Gradl</a> in <i>PicketBox Development</i> - <a href="http://community.jboss.org/message/639028#639028">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>This is a post in a serious of discussions I am starting to get some discussion going on XACML.  I led the implementation of XACML on a large scale using the original SunXACML libraries as the PDP and I am sharing some of my insights as a way to elicit some requirements on the further development of XACML.   The original post and index to these discussions is <a class="" href="http://community.jboss.org/thread/175091?tstart=0">http://community.jboss.org/thread/175091?tstart=0</a>. </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>This thread will discuss policy enforcement.  The core JBoss XACML (PicketBox) portion provides PDP, context handling, and a bit of PIP functionality.  Any PEP capability is elsewhere.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Anil, you mentioned in another thread that PEPs are in higher level projects.  When you get a chance can you let me know where to look for those?    </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Enforcement can be very specific to the resource being protected and to the security environment, but I think there could be some useful pieces that could be provided out of the box.   The first thing is simply an API to simplify making a XACML request.   The majority of enforcement types will only need to deal with a small number of core attributes.. e.g. subject-id, resource-id, action-id.    Additional attributes could be made available more simply as key/value pairs rather than requiring the PEP implementer to construct a complex XACML Request object.  </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The second thing that can be provided is a library of PEPs that can handle common resources, in this case container resources or development framework resources.  For example, you might be able to provide a generalized PEP for an EJB, a servlet, a portlet, etc.   You might have resources in Seam (I'm not very familiar with Seam, so forgive me) but maybe some REST resource or JSF resources (perhaps you want to protect a data field).</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Last thing might be to provide common obligation handling capabilities... maybe must log or something like this.   Plus, the XACML spec states that if a PEP cannot fulfil an obligation it should deny access....if every PEP is written differently, its hard to consistently ensure this is met.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>In all, its hard to provide a set of PEPs that will work for all resources you are protecting, and there's not a ton you can provide here.. but just a couple thoughts/ideas.</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/639028#639028">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in PicketBox Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2088">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>