[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] Identical-Priority XRD "URI" Elements...
The XRI 2.0 spec is about how a resolver returns a service endpoint or points based on the input selection criteria.There is nothing to stop a application from using the endpoints that are returned as it likes.In XRI the SEPs may have refs and redirects so the resolver will always follow the highest priority path.The requesting application should receive all the matching SEPS from the last XRD in the chain, and can do with them as it likes.From an openID point of view I would be opposed to conflating this sort of multi headed authentication with a regular openID authentication. The RP is going to have to be special anyway to achieve this.Define a new Service type and include multiple URI in it. You can create any custom elements you like.
<xrd> <Service> <Type>http://specs.openid.net/auth/2.0/signon</Type> <Type>http://specs.openid.net/extensions/pmae/1.0</Type> <URI>https://op1.example.com/server</URI> <URI>https://op2.example.net/server</URI> </Service> </xrd>
<xrd> <Service> <Type>http://specs.openid.net/auth/2.0/signon</Type> <URI>https://op1.example.com/server</URI> <URI>https://op2.example.net/server</URI> </Service> <Service> <Type>http://specs.openid.net/extensions/pmae/1.0</Type> <URI>https://op1.example.com/server</URI> <URI>https://op2.example.net/server</URI> </Service> </xrd>
<xrd> <Service> <Type priority="10">http://specs.openid.net/auth/2.0/signon</Type> <Type priority="20">http://specs.openid.net/extensions/pmae/1.0</Type> <URI>https://op1.example.com/server</URI> <URI>https://op2.example.net/server</URI> </Service> </xrd>
I think that trying to reuse the existing endpoints in this way is a mistake. The user should clearly indicate that is what they want to have happen in a new SEP like identifier select is a new SEP.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]