27 messages in net.openid.general[OpenID] XRDS multi-OP listing?
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 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[OpenID] XRDS multi-OP listing?Actions...
From:Nat Sakimura (saki@gmail.com)
Date:Jun 5, 2008 8:36:31 pm
List:net.openid.general

XRDS already supports it. It has precedence mechanism just like MX in DNS. Just give lower number to Weaker AuthN OP. Then, it is done.

=nat

On Fri, Jun 6, 2008 at 4:42 AM, SitG Admin <sysadmin at shadowsinthegarden.com> wrote:

It would be better to say "I'd like OP1, but only for PCs, and OP2 for iPhones, ..." all somehow expressed in the XRDS file so the RP could do the redirect to the right OP based on which device I'm using, all while using the same identifier.

On a related note, I'd like it if the XRDS file could (optionally) have multiple OP's identified in such a way that the RP *should* take its cue to (if offering that feature) ask the user which OP they want to use rather than redirecting them right away. I'm not sure but I *think* XRDS would be the right place to start with this; the idea being that, if I had an OP that used one-time-only passwords for authentication, I'd want to save those pre-readied passwords for the situations when I *really* wanted them, and otherwise use a "weaker" OP.

I could also exert some control over my privacy by electing to use OP#1 for my work-related logins, OP#2 for my personal logins, OP#3 for my recreational logins, OP#4 for sites I wasn't sure about yet, and so on. Any visitor to my site could determine which OP's were *possible*, but would have no guarantee that I actually *used* any particular one of them, and compromising the data stored by any single OP would not yield *all* my online activities.

-Shade