<?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>Access Control Service - Common Interaction Model</title><link>http://blogs.msdn.com/justinjsmith/archive/2009/01/16/access-control-service-common-interaction-model.aspx</link><description>In my previous post I described at a high level a simple scenario that leverages the Access Control Service. Now I'd like to describe the interactions between messaging participants and the .NET Access Control Service. Recall the scenario: a multi-tenant</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Access Control Service - Common Interaction Model</title><link>http://blogs.msdn.com/justinjsmith/archive/2009/01/16/access-control-service-common-interaction-model.aspx#9374698</link><pubDate>Sun, 25 Jan 2009 10:19:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9374698</guid><dc:creator>Travis Spencer</dc:creator><description>&lt;p&gt;This blog is way too quite. &amp;nbsp;I know you have TONS of good things to say, Justin. &amp;nbsp;Please do; we're listening and we're eager to hear.&lt;/p&gt;
&lt;p&gt;For instance, I would love to learn more about what happens in step 4 where you say: &amp;quot;There’s a little more to it than that, because the RP has to be able to differentiate its ACS STS from other ACS STSs.&amp;quot; That sounds really fascinating. &amp;nbsp;A blog post on that would be great.&lt;/p&gt;
</description></item></channel></rss>