<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Designing an Authentication and Authorization Strategy</title><link>http://blogs.msdn.com/jmeier/archive/2008/06/25/designing-an-authentication-and-authorization-strategy.aspx</link><description>What are the key steps to designing an effective authentication and authorization strategy? The keys are knowing your user stores, role stores, and who need to access what or perform which operations. In this post, I share the approaches we've used in</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Designing an Authentication and Authorization Strategy</title><link>http://blogs.msdn.com/jmeier/archive/2008/06/25/designing-an-authentication-and-authorization-strategy.aspx#8657211</link><pubDate>Thu, 26 Jun 2008 18:59:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8657211</guid><dc:creator>Adam</dc:creator><description>&lt;p&gt;Why do you say &amp;quot;identities&amp;quot; instead of accounts?&lt;/p&gt;
</description></item><item><title>re: Designing an Authentication and Authorization Strategy</title><link>http://blogs.msdn.com/jmeier/archive/2008/06/25/designing-an-authentication-and-authorization-strategy.aspx#8658435</link><pubDate>Fri, 27 Jun 2008 00:34:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8658435</guid><dc:creator>J.D. Meier</dc:creator><description>&lt;p&gt;I tend to think of accounts as implementation of my identities.&lt;/p&gt;
</description></item></channel></rss>