<?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>Simplify User Access, Secure Collaboration Across Organizational Boundaries with ‘Geneva’ Beta 2</title><link>http://blogs.msdn.com/usisvde/archive/2009/05/12/simplify-user-access-secure-collaboration-across-organizational-boundaries-with-geneva-beta-2.aspx</link><description>One of the biggest challenges facing ISVs how to deal with the identity of the users and what information they are allowed to have access to. When you add the idea of securing access between organizations, it gets more complex. But users want single sign</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Secure ID – gets a work around with support from key vendors</title><link>http://blogs.msdn.com/usisvde/archive/2009/05/12/simplify-user-access-secure-collaboration-across-organizational-boundaries-with-geneva-beta-2.aspx#9707584</link><pubDate>Mon, 08 Jun 2009 09:30:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9707584</guid><dc:creator>CTO Blog</dc:creator><description>&lt;p&gt;A secure ID is one of the key underlying systems for most in-house IT systems, but as we move into a Web 2.0 world, does this go far enough? We really need a federated ID that is still secure for...&lt;/p&gt;
</description></item></channel></rss>