<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Active Directory Federation Services (ADFS) Step-by-Step Guide</title>
	<atom:link href="http://artduane.wordpress.com/2007/08/29/active-directory-federation-services-adfs-step-by-step-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://artduane.wordpress.com/2007/08/29/active-directory-federation-services-adfs-step-by-step-guide/</link>
	<description>Mastering Powerful Software &#38; Web Site.</description>
	<lastBuildDate>Sun, 04 Jan 2009 17:02:10 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric Tronson</title>
		<link>http://artduane.wordpress.com/2007/08/29/active-directory-federation-services-adfs-step-by-step-guide/#comment-3</link>
		<dc:creator>Eric Tronson</dc:creator>
		<pubDate>Fri, 21 Sep 2007 10:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://artduane.wordpress.com/2007/08/29/active-directory-federation-services-adfs-step-by-step-guide/#comment-3</guid>
		<description>I love this! I recommend you pay an attention to the appendix A at the bottom of this document discussing the aspects of using Federation Services with Sharepoint Portal Server 2003. I don&#039;t know why the OSS 2007 wasn&#039;t included in the document but that doesn&#039;t matter as Office Sharepoint Server 2007 is far more powerful in terms on security and administration. But as is the norm, the advances that appear in such technology concepts and implementations like this tends to impose the corresponding requirements on the remaining part of the instrumentation involved into the process. As for me, I see it like it demands us to  think more about preparing security measures to control the site security and watch the assignment of the permission throughout the sites hosted on the SharePoint sites. That&#039;s reasonable but the standard administration control is mum about the security structure and revealing the security holes caused by misuse of permission management appears to be a complicated task. It could be that for a developer it&#039;s preferable to implement all from scratch although a friend of mine who&#039;s into programming sharepoint web-parts says he don&#039;t like spending the time to manipulate security access settings while testing his applications. Me, being the administrator who maintains some operations on our corporate sites, I want everything to be clear and easily reviewed. Recently I stumbled upon the nice &lt;a HREF=&quot;http://www.scriptlogic.com/products/security-explorer/sharepoint/&quot; REL=&quot;nofollow&quot;&gt;Security Explorer&lt;/a&gt; tool from Scriptlogic that has a special control tools to perform permission management for item-level security, and observe the security for all sites within the farm. It seriously remediates the clutter of administering security on several sites that we host here in our company.</description>
		<content:encoded><![CDATA[<p>I love this! I recommend you pay an attention to the appendix A at the bottom of this document discussing the aspects of using Federation Services with Sharepoint Portal Server 2003. I don&#8217;t know why the OSS 2007 wasn&#8217;t included in the document but that doesn&#8217;t matter as Office Sharepoint Server 2007 is far more powerful in terms on security and administration. But as is the norm, the advances that appear in such technology concepts and implementations like this tends to impose the corresponding requirements on the remaining part of the instrumentation involved into the process. As for me, I see it like it demands us to  think more about preparing security measures to control the site security and watch the assignment of the permission throughout the sites hosted on the SharePoint sites. That&#8217;s reasonable but the standard administration control is mum about the security structure and revealing the security holes caused by misuse of permission management appears to be a complicated task. It could be that for a developer it&#8217;s preferable to implement all from scratch although a friend of mine who&#8217;s into programming sharepoint web-parts says he don&#8217;t like spending the time to manipulate security access settings while testing his applications. Me, being the administrator who maintains some operations on our corporate sites, I want everything to be clear and easily reviewed. Recently I stumbled upon the nice <a HREF="http://www.scriptlogic.com/products/security-explorer/sharepoint/" REL="nofollow">Security Explorer</a> tool from Scriptlogic that has a special control tools to perform permission management for item-level security, and observe the security for all sites within the farm. It seriously remediates the clutter of administering security on several sites that we host here in our company.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
