<?xml version="1.0" encoding="UTF-8"?>
<rss version='2.0'>
	<channel>
		<title>OpenID Forum Software and More to Identify you</title>
		<link>http://openidforum.com/</link>
		<description>RSS 2.0 feed of OpenID Forum Software and More to Identify you</description>
		<language>en</language>
		<generator>IceBB</generator>

		<item>
			<title>To implement openID,etc then pricing is per mo or yr?</title>
			<description>
<![CDATA[
To implement<br />
<a href='http://getsatisfaction.com/'>http://getsatisfaction.com/</a> includes openID<br />
or openID only<br />
then pricing is per mo or yr?<br />
may get only the service of log-in to my site, via other site (facebook, google,...,openID) and nothing more?
]]>
			</description>
			<link>http://openidforum.com/index.php?topic=4&amp;pid=6</link>
			<pubDate>Tue, 15 Mar 2011 22:02:21 +0100</pubDate>
			<author>lse123</author>
			<guid isPermaLink='false'>6</guid>
		</item>
		<item>
			<title>Re: How can an &quot;immediate request&quot; be useful?</title>
			<description>
<![CDATA[
Hi zeitgeist09,<br />
I&#39;m not sure I can help you, but since I am very interested in "immediate mode" and don&#39;t fully understand it, I try anyway, and hopefully we find the answer together.<br />
<br />
I went to facebook after reading your post, because I knew, fb is using immediate mode.<br />
<br />
If you can&#39;t imagine how the immediate mode can be usefull, then read this: <a href='http://www.insidefacebook.com/2009/05/18/facebook-launches-openid-support-users-can-now-login-with-a-gmail-account/'>http://www.insidefacebook.com/2009/05/18/facebook-launches-openid-support-users-can-now-login-with-a-gmail-account/</a> , especially the part about "it’s important for us not to send them off to a site and have a bad experience".<br />
<br />
Now if you go to facebook.com and turn on some sniffer, e.g. wireshark, you may see what requests are issued...your browser issues openid auth requests to all openid accounts, which are associated with your fb account (accounts which you linked to fb under settings). I use/linked myopenid.com and my browser issues following request:<br />
GET /server?openid.assoc_handle=%7BHMAC-SHA1%7D%7B4b1d73a2%7D%7BsDOQdg%3D%3D%7D&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_immediate&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.ui=http%3A%2F%2Fspecs.openid.net%2Fextensions%2Fui%2F1.0&openid.realm=https%3A%2F%2Fwww.facebook.com%2F&openid.return_to=https%3A%2F%2Fwww.facebook.com%2Fopenid%2Freceiver.php%3Fprovider_id%3D1010459836373%26protocol%3Dhttp%26context%3Dbackground_login%26request_id%3D1&openid.ui.icon=true&openid.ui.mode=popup HTTP/1.1<br />
Host: <a href='http://www.myopenid.com'>www.myopenid.com</a><br />
...<br />
<br />
The immediate mode presumes, that i am logged in at myopenid.com and since my browser is issuing the request, myopenid checks my cookies and should know it&#39;s me. Second prerequisite is, that i approved for fb to make immediate requests, so none approval is neccessary and mopenid responses with an authentication response (basically just "yes" or "no"), though I&#39;m not sure about how this response is then associated with the fb window. i&#39;d like to know, how exactly fb gets the response from myopenid.com. I guess it&#39;s an ajax request and the response can be then parsed by js and send to fb in another ajax request, fb then sees if the response was positive and checks signature. if it is valid, fb redirects you with javascript to your account as a &#39;logged in&#39; user. but keep in mind, that i only assume it works this way!<br />
<br />
I hope it was at least a little helpful!<br />
<br />
regards,<br />
sovo
]]>
			</description>
			<link>http://openidforum.com/index.php?topic=3&amp;pid=5</link>
			<pubDate>Thu, 17 Dec 2009 00:13:48 +0100</pubDate>
			<author>sovo</author>
			<guid isPermaLink='false'>5</guid>
		</item>
		<item>
			<title>How can an &quot;immediate request&quot; be useful?</title>
			<description>
<![CDATA[
Hello there,<br />
<br />
I think I clearly got the concept of OpenID-Authentication-2.0. But while thinking of the Authentication-Request-Response process I really can not imagine how "immediate requests" can be useful.<br />
<br />
This kind of request works without user interaction. What happens in the end is to my understanding that the RP checks the user claimed identifier without verifying the user&#39;s identity. Maybe he has already checked the identity but why should he afterwards check the identifier again? To make sure that the user still exists without bothering him again with some authentication/identification process? I don&#39;t get it.<br />
<br />
So, it would be nice to have a little discussion about this or better: an expert answere  :) <br />
<br />
Greetings,<br />
zeitgeist09
]]>
			</description>
			<link>http://openidforum.com/index.php?topic=3&amp;pid=4</link>
			<pubDate>Fri, 04 Dec 2009 15:31:16 +0100</pubDate>
			<author>zeitgeist09</author>
			<guid isPermaLink='false'>4</guid>
		</item>
		<item>
			<title>Final Draft for OpenID 2.0</title>
			<description>
<![CDATA[
Abstract<br />
<br />
OpenID Authentication provides a way to prove that an end user controls an Identifier. It does this without the Relying Party needing access to end user credentials such as a password or to other sensitive information such as an email address.<br />
<br />
OpenID is decentralized. No central authority must approve or register Relying Parties or OpenID Providers. An end user can freely choose which OpenID Provider to use, and can preserve their Identifier if they switch OpenID Providers.<br />
<br />
While nothing in the protocol requires JavaScript or modern browsers, the authentication scheme plays nicely with "AJAX"-style setups. This means an end user can prove their Identity to a Relying Party without having to leave their current Web page.<br />
<br />
OpenID Authentication uses only standard HTTP(S) requests and responses, so it does not require any special capabilities of the User-Agent or other client software. OpenID is not tied to the use of cookies or any other specific mechanism of Relying Party or OpenID Provider session management. Extensions to User-Agents can simplify the end user interaction, though are not required to utilize the protocol.<br />
<br />
The exchange of profile information, or the exchange of other information not covered in this specification, can be addressed through additional service types built on top of this protocol to create a framework. OpenID Authentication is designed to provide a base service to enable portable, user-centric digital identity in a free and decentralized manner.<br />
<br />
<a href='http://openid.net/specs/openid-authentication-2_0.html'>Complete document here.</a>
]]>
			</description>
			<link>http://openidforum.com/index.php?topic=2&amp;pid=3</link>
			<pubDate>Mon, 11 Aug 2008 01:01:33 +0200</pubDate>
			<author>okID</author>
			<guid isPermaLink='false'>3</guid>
		</item>
		<item>
			<title>FeedBack</title>
			<description>
<![CDATA[
Signup for <a href='http://okid.me'>OKid.ME</a><br />
<br />
Usage username.okid.me in any OpenID enabled website.<br />
<br />
At the Prompt enter your username and password. Once you have logged in, your credentials are good for any other OpenID website you visit.<br />
<br />
To Delete your secure session @ public terminals etc, close the browser window. :D
]]>
			</description>
			<link>http://openidforum.com/index.php?topic=1&amp;pid=2</link>
			<pubDate>Fri, 08 Aug 2008 07:02:13 +0200</pubDate>
			<author>Shaman</author>
			<guid isPermaLink='false'>2</guid>
		</item>

	</channel>
</rss>
