<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Finally: an open XACML API!</title>
	<atom:link href="http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/</link>
	<description>Kuppinger Cole + Partner</description>
	<lastBuildDate>Thu, 14 Jan 2010 23:53:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: links for 2009-08-05 &#8226; Bare Identity</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/comment-page-1/#comment-86</link>
		<dc:creator>links for 2009-08-05 &#8226; Bare Identity</dc:creator>
		<pubDate>Thu, 06 Aug 2009 00:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/#comment-86</guid>
		<description>[...] Finally: an open XACML API! &#124; Felix Gaehtgens &quot;Microsoft has made it truly “dead easy” for developers to make their applications ready for externalised authentication and claims – with just a few lines of “plumbing code”. Externalising authorisation must be made just as simple. The XACML API is a great start to provide a foundation that can be used to connect simpler APIs and existing access control frameworks to XACML.&quot; (tags: kuppingercole felixgaehtgens xacml abac) [...]</description>
		<content:encoded><![CDATA[<p>[...] Finally: an open XACML API! | Felix Gaehtgens &quot;Microsoft has made it truly “dead easy” for developers to make their applications ready for externalised authentication and claims – with just a few lines of “plumbing code”. Externalising authorisation must be made just as simple. The XACML API is a great start to provide a foundation that can be used to connect simpler APIs and existing access control frameworks to XACML.&quot; (tags: kuppingercole felixgaehtgens xacml abac) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Felix Gaehtgens</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/comment-page-1/#comment-85</link>
		<dc:creator>Felix Gaehtgens</dc:creator>
		<pubDate>Wed, 05 Aug 2009 09:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/#comment-85</guid>
		<description>Good point there, thanks Bjorn! 
The JBoss XACML API is another good example of a XACML API that can be used from inside application servers. It support XACML v2.0 (at this point), and is specifically geared towards Java application servers. There are actually quite a few APIs out there - almost every XACML access/entitlement engine has its own set of APIs. 
 
I continue to believe that we actually need a whole API stack: from a very low-level API that is very close to the XACML policy language up to a high-level API that makes it really easy for developers to externalise their authorisation decisions. I think the OASIS API is a very nice fit for the low-level API because it is very close to the actual XACML semantics. The JBOSS API is somewhere in the middle, allowing developers to use XACML directly by implementing also some convenience functions. I&#039;m still looking for a high-level API, potentially with some tooling for common IDEs that make it virtually trivial for developers to separate authorisation out. </description>
		<content:encoded><![CDATA[<p>Good point there, thanks Bjorn!</p>
<p>The JBoss XACML API is another good example of a XACML API that can be used from inside application servers. It support XACML v2.0 (at this point), and is specifically geared towards Java application servers. There are actually quite a few APIs out there &#8211; almost every XACML access/entitlement engine has its own set of APIs.</p>
<p>I continue to believe that we actually need a whole API stack: from a very low-level API that is very close to the XACML policy language up to a high-level API that makes it really easy for developers to externalise their authorisation decisions. I think the OASIS API is a very nice fit for the low-level API because it is very close to the actual XACML semantics. The JBOSS API is somewhere in the middle, allowing developers to use XACML directly by implementing also some convenience functions. I&#039;m still looking for a high-level API, potentially with some tooling for common IDEs that make it virtually trivial for developers to separate authorisation out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bj&#248;rn Ola Smievoll</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/comment-page-1/#comment-84</link>
		<dc:creator>Bj&#248;rn Ola Smievoll</dc:creator>
		<pubDate>Tue, 04 Aug 2009 23:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.com/gaehtgens/2009/07/31/finally-an-open-xacml-api/#comment-84</guid>
		<description>It&#039;s truly great that more impls exists, but shouldn&#039;t the JBoss XACML API also be considered as free and open source software?  &lt;a href=&quot;http://www.jboss.org/jbosssecurity/download/index.html&quot; target=&quot;_blank&quot;&gt;http://www.jboss.org/jbosssecurity/download/index...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>It&#039;s truly great that more impls exists, but shouldn&#039;t the JBoss XACML API also be considered as free and open source software?  <a href="http://www.jboss.org/jbosssecurity/download/index.html" target="_blank"></a><a href="http://www.jboss.org/jbosssecurity/download/index.." rel="nofollow">http://www.jboss.org/jbosssecurity/download/index..</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
