openid_url as query parameter

[Sam Alexander]

The only problem I would see with this is that we'd have people whose  
bookmarks all pointed to www.site.com/?openid_url=http://openidurl.com.

For people who share bookmarks, or use bookmarking services like  
del.icio.us, that would lessen the relevance of each individual  
bookmark -- each user would have to store their own customized link.

However, the flow you're talking about is entirely possible.  I think  
the best way for OpenID Reliers to implement it is to store a cookie  
with the user's OpenID in it.  Then when the user goes to the site,  
the Relier can fire off a "check_immediate" request.  A  
"check_immediate" request basically asks "Hey, is this user already  
logged in to their provider, and if so, can I log them in to my site  
without hassling them?".  If Provider answers "yes", the user is  
logged in without the redirection steps.  Otherwise, if the answer is  
"no", the Relier can proceed with just a normal form-based login.

This way, we all still have bookmarks that point to "http:// 
www.sudokular.com/", and the bookmarking services can keep track of  
that single url.

-Sam

On Sep 13, 2007, at 10:33 AM, news letter wrote:

> Dear OpenID enthousiasts,
>
> I have visited some OpenID enabled sites. I have found that they  
> require submitting a form with my OpenID to get the process going.  
> I'm no expert and neither a heavy OpenID user. But I was wondering  
> what would happen if the OpenID enabled website could support  
> adding my OpenID as a request parameter?
>
> Instead of this flow:
> 1. Http GET request for http://myenabledsite.com/index.php
> 2. Fill in OpenID in form and click Submit
> 3. OpenID processing (possibly requiring authentication)
> 4. Logged in to myenabledsite.com
>
> I would get this flow:
> 1. Http GET request for http://myenabledsite.com/index.php? 
> openid_url=http://getopenid.com/sampleid
> 2. OpenID processing (possibly requiring authentication)
> 3. Logged in to myenabledsite.com
>
> I would eliminate step 2 of the orginal process.
> I could bookmark my favourite Open-ID enabled sites with the  
> request parameter added, never having to fill in the form anymore.
> If I was logged in to my OpenID provider already, I would have a  
> 'true' Single Sign-On experience.
>
> It's hard to imagine I would be the first to think of this and  
> there are probably good reasons not to implement OpenID like this.  
> So I am very curious as to what those reasons are.
> Two, I could think of myself are:
> 1. that this request parameter would have to be standardised in a  
> way so that users wouldn't have to 'guess' at it
> 2. that you would still have to find out which page to GET with the  
> request parameter. Not all sites 'start' at /index.php. A possible  
> solution for this would be not to use a request parameter but a  
> standard URL. You would be able to login with OpenID to every  
> enabled site at http://<domain>/openid/<your openid>.
>
> Thanks in advance for your feedback.
>
> Kind regards,
> Robin
> _______________________________________________
> user-experience mailing list
> user-experience at openid.net
> http://openid.net/mailman/listinfo/user-experience

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-user-experience/attachments/20070913/03708cd4/attachment-0002.htm>