atom feed27 messages in net.openid.general[OpenID] An OpenID "mobile" Hint?
FromSent OnAttachments
David RecordonJun 4, 2008 2:08 pm 
Hans GranqvistJun 4, 2008 2:34 pm 
David RecordonJun 4, 2008 4:50 pm 
Johannes ErnstJun 4, 2008 9:49 pm 
Nat SakimuraJun 4, 2008 11:51 pm 
Martin AtkinsJun 5, 2008 12:02 am 
Kick WillemseJun 5, 2008 3:49 am 
Steven Livingstone-PerezJun 5, 2008 4:06 am 
SitG AdminJun 5, 2008 8:31 am 
Johannes ErnstJun 5, 2008 9:15 am.gif, .gif
David RecordonJun 5, 2008 9:50 am 
David RecordonJun 5, 2008 9:51 am 
Martin AtkinsJun 5, 2008 10:35 am 
SitG AdminJun 5, 2008 12:42 pm 
Martin AtkinsJun 5, 2008 1:34 pm 
SitG AdminJun 5, 2008 3:58 pm 
Nat SakimuraJun 5, 2008 6:59 pm 
Nat SakimuraJun 5, 2008 7:06 pm 
Nat SakimuraJun 5, 2008 8:36 pm 
Martin AtkinsJun 6, 2008 12:06 am 
Johannes ErnstJun 6, 2008 3:08 pm 
Warren JamisonJun 6, 2008 6:05 pm 
Carsten PötterJun 6, 2008 8:47 pm 
Brandon RamirezJun 7, 2008 10:28 am 
Brandon RamirezJun 7, 2008 10:33 am 
SitG AdminJun 7, 2008 9:22 pm 
Tan, WilliamJun 16, 2008 10:57 am 
Subject:[OpenID] An OpenID "mobile" Hint?
From:Nat Sakimura (saki@gmail.com)
Date:Jun 5, 2008 7:06:15 pm
List:net.openid.general

OK. Got it.

So, you probably mean that there should be some kind of support type listed in the XRDS so that RP can choose an appropriate OP just like in PAPE's case.

I agree that it will be very useful.

Just like PAPE, I suppose the RP will request OP with specific capability, in this case, that of device, e.g., screen size, color capability, etc.

Actually, I suppose this can be united with language preference proposal as well. It is just a capability based selection and request.

Any plan on WG?

=nat

On Fri, Jun 6, 2008 at 1:51 AM, David Recordon <drecordon at sixapart.com>
wrote:

Agreed, in a perfect world you'd have lots of OPs with mobile experiences. I guess part of what I'm thinking about is far less around the technology and more around a forcing function to make it very clear about which OPs support mobile and which don't. In the end hopefully getting us to that perfect world.

--David

On Jun 5, 2008, at 12:03 AM, Martin Atkins wrote:

Maybe I'm misunderstanding what you're looking at here, but surely anything that the RP can "see" to determine whether you're on a mobile device can also be seen by the OP? They're both just websites, after all.

Having the RP be responsible for switching on provider seems like the wrong approach to me. I'd rather just pick an OP that has good mobile support and know that it'll always work than have spotty support across RPs and never know quite what it's going to do. If your provider doesn't work well on your mobile device, you should switch to a provider that does.

What's the advantage of having the RP determine that you're "on a mobile" vs. the OP?

David Recordon wrote:

In developing a mobile application that uses OpenID for logins one of the things I've become really cognizant of is how poor of the mobile experience most Providers have when it comes to OpenID. It obviously doesn't take a lot to create a streamlined Provider flow for authentication and the trust request, but so far it seems that no one has really done that. I was also thinking more about Providers such as YubiKey where authenticating with a USB device (despite how awesome it is) won't work on my iPhone.

I'm wondering if it would be useful to write a dead simple extension to provide some hints around mobile support? Allow a Provider to advertise in an XRDS file that they support a mobile login flow so that Relying Parties could discover that theoretically making it so that I could use a Provider such as YubiKey on the desktop and then MyOpenID on the phone.

Am I barking up a useful tree? If I spec'd this would any Providers actually implement a mobile friendly flow?