Another thought: since a responsible RP only creates a single association with an OP and stores it until it expires, and these associations often last days, if the user has an endpoint in the XRDS doc that points to an OP that is currently down, but with whom the RP has an existing, unexpired association with, the RP shouldn't try to create an association with that OP. Instead, it might say to itself "yes, I successfully have an association with this OP, so I'll redirect the user to it", but the OP happens to be down for 5 hours that day, effectively disabling the user's ability to log in, in spite of the multiple OPs listed in the XRDS doc.<br>
<br>So... perhaps OpenID can have a "ping, are you alive?" message in its protocol. But then we're no better than "dumb" RPs having to make multiple hits to the OP instead of just one. <br><br>Another idea that keeps occuring to me is that the RP can use a frameset to keep an RP frame around and have the OP authentication happen in another frame (iframe or frameset would work). That way, the RP frame could have something like "Is your Provider not responding? Click here to try your next best choice..." or something to that effect. The problem with this idea is that the URL on the browser will always be the RP, so the user will have one less way to confirm that this is indeed his genuine Provider and not one of those notorious OpenID RP phishing attacks.<br>
<br>Anyone have any idea how to solve this dead OP problem?<br><br><div class="gmail_quote">On Tue, Jul 15, 2008 at 1:52 AM, James Tindall <<a href="mailto:james@atomless.com">james@atomless.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've recently been writing an openid relying party library for the<br>
Kohana php framework and I think you're right, the way I've tried to<br>
handle multiple enpoints returned from the discovery phase is to first<br>
sort them by their priority values and then also filter out any that do<br>
not meet the (extension / security / openid-version) requirements set in<br>
the current relying party configuration and then finally attempt to<br>
establish an association with each endpoint in turn until a successfull<br>
association response is returned.<br>
<br>
I feel that all this is best done invisibly rather than requesting the<br>
user to jump through extra hoops. The user has after all -at some point-<br>
set the priority of the endpoints listed in the xrds and I suspect that<br>
most would not wish for further input during the process of<br>
authentication. My assumption being that the point of multiple endpoints<br>
is to hopefully cater for the requirements of as many different relying<br>
parties as possible and to have alternative/backup endpoints incase of<br>
errors or failures with any of the other endpoints in the list during<br>
authentication?<br>
<br>
=james.tindall<br>
<div class="Ih2E3d"><br>
Andrew Arnott wrote:<br>
> I'm curious how other libraries do (or plan to) handle multiple endpoints in<br>
> a single XRDS document. I see a few considerations, in order:<br>
><br>
</div>> 1. Enumerate the services in the XRDS-defined priority order<br>
> 2. Skip the services that do not expose OpenID endpoints.<br>
> 3. Skip the OpenID endpoints with Providers that do not quality<br>
<div class="Ih2E3d">> (whitelist/blacklist or advertised extension support<br>
</div>> 4. Take the first endpoint that is left after these filters.<br>
<div class="Ih2E3d">><br>
> But what about the rest of the endpoints listed? Here are some<br>
> possibilities:<br>
><br>
</div>> 1. Just use the first endpoint and trust it works.<br>
> 2. Try each one successively. That is, the RP should attempt to<br>
<div class="Ih2E3d">> establish an association with each one until it succeeds with one, and then<br>
> redirect the user to that one for authentication. Redirecting the user to<br>
> an unavailable Provider will result in a dead end failure page and the RP<br>
> will lose the opportunity at this point to try the next endpoint.<br>
</div>> 3. A variant on the last, except that in addition to skipping OPs that do<br>
<div class="Ih2E3d">> not respond to association requests, allow the user to "fail" or cancel the<br>
> authentication on the first provider and proceed to the second provider<br>
> listed for another authentication attempt.<br>
</div>> 4. Offer the user a list of his/her providers to choose from for<br>
<div class="Ih2E3d">> authentication.<br>
><br>
> Have thoughts been written already on which of these are best and/or common<br>
> in existing libraries?<br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> general mailing list<br>
> <a href="mailto:general@openid.net">general@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
><br>
<br>
--<br>
<br>
-----------------------------------------<br>
<br>
James Tindall<br>
<br>
<a href="http://www.atomless.com/" target="_blank">http://www.atomless.com/</a><br>
<br>
T : +44(0)1305 250 377<br>
M : +44(0)7971 012 032<br>
F : +44(0)1305 250 377<br>
<br>
-----------------------------------------<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</blockquote></div><br>