<?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"
	>
<channel>
	<title>Comments on: Analysis of OpenID implementations</title>
	<atom:link href="http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/feed/" rel="self" type="application/rss+xml" />
	<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/</link>
	<description>News and Updates on the Community.</description>
	<pubDate>Sat, 06 Sep 2008 16:38:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Tamlyn</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1339</link>
		<dc:creator>Tamlyn</dc:creator>
		<pubDate>Mon, 11 Feb 2008 10:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1339</guid>
		<description>(fixed the URLs)

PiP is quite interesting. I was impressed by the granular control of the simple registration extension, i.e. you can choose exactly which details to expose to the Relying Party, but I missed having a "complete all fields" button. The ability to set a date on which your 'trust' for the Relying Party will expire (i.e. after which you will need to re-authorise it) seems a bit unnecessary. It may also give the false impression that your account at the site of the Relying party will be terminated after that date or that they will no longer have access to your information.

There appear to be lots of other features to tie in with VeriSign's identity services but I haven't had a chance to check them out yet.</description>
		<content:encoded><![CDATA[<p>(fixed the URLs)</p>
<p>PiP is quite interesting. I was impressed by the granular control of the simple registration extension, i.e. you can choose exactly which details to expose to the Relying Party, but I missed having a "complete all fields" button. The ability to set a date on which your 'trust' for the Relying Party will expire (i.e. after which you will need to re-authorise it) seems a bit unnecessary. It may also give the false impression that your account at the site of the Relying party will be terminated after that date or that they will no longer have access to your information.</p>
<p>There appear to be lots of other features to tie in with VeriSign's identity services but I haven't had a chance to check them out yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1334</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Sun, 10 Feb 2008 20:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1334</guid>
		<description>Remove the .'s from the end of the URLs ;)</description>
		<content:encoded><![CDATA[<p>Remove the .'s from the end of the URLs <img src='http://community.plus.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LiamM</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1333</link>
		<dc:creator>LiamM</dc:creator>
		<pubDate>Sun, 10 Feb 2008 19:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1333</guid>
		<description>Hmmm, neither of those pages work for me, Gary.</description>
		<content:encoded><![CDATA[<p>Hmmm, neither of those pages work for me, Gary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1300</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Sat, 09 Feb 2008 16:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1300</guid>
		<description>Thanks Gary, we'll check that out!</description>
		<content:encoded><![CDATA[<p>Thanks Gary, we'll check that out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Krall</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1271</link>
		<dc:creator>Gary Krall</dc:creator>
		<pubDate>Fri, 08 Feb 2008 20:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1271</guid>
		<description>Hi:  As the technical director for the OpenID development here at Verisign I would be remiss if I did not ask you to check out our implementation.

Our Identity provider called the "PiP" is located at:  https://pip.verisignlabs.com  I would also encourage you to check out or Firefox extension called "SeatBelt" which can be located at:  https://pip.verisignlabs.com/seatbelt.do

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi:  As the technical director for the OpenID development here at Verisign I would be remiss if I did not ask you to check out our implementation.</p>
<p>Our Identity provider called the "PiP" is located at:  <a href="https://pip.verisignlabs.com" rel="nofollow">https://pip.verisignlabs.com</a>  I would also encourage you to check out or Firefox extension called "SeatBelt" which can be located at:  <a href="https://pip.verisignlabs.com/seatbelt.do" rel="nofollow">https://pip.verisignlabs.com/seatbelt.do</a></p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LiamM</title>
		<link>http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1265</link>
		<dc:creator>LiamM</dc:creator>
		<pubDate>Fri, 08 Feb 2008 17:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://community.plus.net/blog/2008/02/08/analysis-of-openid-implementations/#comment-1265</guid>
		<description>Interesting that this appeared on the Beeb site today :-

http://news.bbc.co.uk/1/hi/technology/7234499.stm</description>
		<content:encoded><![CDATA[<p>Interesting that this appeared on the Beeb site today :-</p>
<p><a href="http://news.bbc.co.uk/1/hi/technology/7234499.stm" rel="nofollow">http://news.bbc.co.uk/1/hi/technology/7234499.stm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
