<?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: Audience Targeting in Windows SharePoint Services 3.0, based on AD Groups</title>
	<atom:link href="http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-wss/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-wss/</link>
	<description>Trends and insight into legal technology, infrastructure and strategic thinking.</description>
	<lastBuildDate>Thu, 02 Feb 2012 13:59:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michael Fettner</title>
		<link>http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-wss/comment-page-1/#comment-112</link>
		<dc:creator>Michael Fettner</dc:creator>
		<pubDate>Wed, 17 Feb 2010 15:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-windows-sharepoint-services-3-0-based-on-ad-groups/#comment-112</guid>
		<description>Hi Mike.  You could certainly do this kind of targeting on pages to a .Net membership provider.  Instead of adding code to query System.DirectoryServices, you would just query the membership provider or SharePoint groups directly with the SharePoint api.

From your other message, it sounds like you want to prohibit users from seeing other members in their group, which is more tricky.  The default security only lets you choose to expose group members to everyone or just other group members.

I think you would have to create a feature to hide all of the “people and groups” links, or attempt to modify “/_layouts/people.aspx,” which is not a best practice.  You could also check the object model to see if there is a programmatic way to change the group settings security.</description>
		<content:encoded><![CDATA[<p>Hi Mike.  You could certainly do this kind of targeting on pages to a .Net membership provider.  Instead of adding code to query System.DirectoryServices, you would just query the membership provider or SharePoint groups directly with the SharePoint api.</p>
<p>From your other message, it sounds like you want to prohibit users from seeing other members in their group, which is more tricky.  The default security only lets you choose to expose group members to everyone or just other group members.</p>
<p>I think you would have to create a feature to hide all of the “people and groups” links, or attempt to modify “/_layouts/people.aspx,” which is not a best practice.  You could also check the object model to see if there is a programmatic way to change the group settings security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-wss/comment-page-1/#comment-111</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sun, 14 Feb 2010 05:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kraftkennedy.com/index.php/2009/07/13/audience-targeting-in-windows-sharepoint-services-3-0-based-on-ad-groups/#comment-111</guid>
		<description>Hello,
Interesting article.  Do you think you could implement audience targeting in WSS using a .NET membership provider instead of an AD?

Please let me know.

Thanks,
Mike</description>
		<content:encoded><![CDATA[<p>Hello,<br />
Interesting article.  Do you think you could implement audience targeting in WSS using a .NET membership provider instead of an AD?</p>
<p>Please let me know.</p>
<p>Thanks,<br />
Mike</p>
]]></content:encoded>
	</item>
</channel>
</rss>

