<?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: Enter your “User name and Password”, what an annoying thing to ask</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itproject/enter-your-%e2%80%9cuser-name-and-password%e2%80%9d-what-an-annoying-thing-to-ask/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itproject/enter-your-%e2%80%9cuser-name-and-password%e2%80%9d-what-an-annoying-thing-to-ask/</link>
	<description></description>
	<pubDate>Fri, 19 Mar 2010 16:45:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jameeliqbal</title>
		<link>http://itknowledgeexchange.techtarget.com/itproject/enter-your-%e2%80%9cuser-name-and-password%e2%80%9d-what-an-annoying-thing-to-ask/#comment-96</link>
		<dc:creator>Jameeliqbal</dc:creator>
		<pubDate>Mon, 16 Nov 2009 18:50:14 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itproject/?p=474#comment-96</guid>
		<description>I do agree with you.  Lately, single sign-on feature is being adopted slowly and steadily.  Organizations like open id (http://openid.net/) and RPX (https://rpxnow.com/) are leading the intiative.  Using thier api, developers can implement single-sign on features into thier websites.

For example, in the site i am developing right now (www.ayushmenon.com/cms/index.php/blog) it requires a user to login in order to comment on the blog.  But he/she does not have to register on the website.  Instead he/she can login using any of his/her gmail/yahoo/facebook id.  

All other info which I want to collect from the person who comments, is provided by the provider of the id (gmail, yahoo etc).  But all this is transparent to the commentor.</description>
		<content:encoded><![CDATA[<p>I do agree with you.  Lately, single sign-on feature is being adopted slowly and steadily.  Organizations like open id &nbsp;&lt;a href="http://openid.net/" title="http://openid.net/" target="_blank"&gt;http://openid.net/&lt;/a&gt;) and RPX &nbsp;&lt;a href="https://rpxnow.com/" title="https://rpxnow.com/" target="_blank"&gt;https://rpxnow.com/&lt;/a&gt;) are leading the intiative.  Using thier api, developers can implement single-sign on features into thier websites.</p>
<p>For example, in the site i am developing right now &nbsp;&lt;a href="http://www.ayushmenon.com" title="http://www.ayushmenon.(" target="_blank"&gt;www.ayushmenon.com&lt;/a&gt;) it requires a user to login in order to comment on the blog.  But he/she does not have to register on the website.  Instead he/she can login using any of his/her gmail/yahoo/facebook id.  </p>
<p>All other info which I want to collect from the person who comments, is provided by the provider of the id (gmail, yahoo etc).  But all this is transparent to the commentor.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->