[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] HXRI as OpenID
Let me ask you this: are both approaches
XRI Resolution compliant? I really don’t like #2 because it forces users
to do something new (ie add “openid.” At the beginning) *and*, technically speaking, the identifier
is no longer an HXRI. I’d especially prefer Markus’
solution if it were still compliant with XRI Resolution. -Gabe From: Drummond Reed
[mailto:drummond.reed@cordance.net] Markus, Gabe: Both suggestions have serious merit.
Neither is perfect, but given that we are working the Yadis requirements into
XRI Resolution 2.0 Working Draft 11 as we went over last week, we need to
provide a clear answer as to how XRIs in HXRI format can work with any version
of OpenID. The openid.xri.net special-proxy-address
option was the one I discussed at breakfast last week – I don’t
think its very “hacky” since all it involves is using a known
“special proxy” to modify the HXRI to produce an OpenID-compliant
proxy request to xri.net. However Markus’s suggestion bears serious
scrutiny as it doesn’t require i-name users to learn anything new other
than what they already know about how to use their i-name as a URL (i.e., put
“xri.net/” in front of it). Others on the TC: which you prefer of
these two solutions to the issue of how i-names can be made compatible with any
OpenID Relying Party, even if they don’t have direct XRI support? Let us
know by replying to this message whether you prefer: 1) Modifying HXRI proxy servers to provide
OpenID/Yadis-compliant responses if no User-Agent header is present in the
request. (In this case the proxy would return both an X-XRDS-Location header
and an XRDS document.) 2) Using a special OpenID-enabled proxy
server address such as openid.xri.net. (In this case the special proxy would
simply add the query parameters to the HXRI to return an XRDS to the request,
then redirect the request to the normal proxy server.) =Drummond From: An even hackier solution might be to give
your xri as openid.xri.net/<yourxri> (which is NOT an HXRI – it
would resolve in a special way for ignorant OpenID 1.X RPs’). This
requires user intervention, so it’s not a really good solution.
-Gabe From:
markus.sabadello@gmail.com [mailto:markus.sabadello@gmail.com] On Behalf Of Markus Sabadello One more thing today.. I
had an idea about the problem Drummond mentionned during breakfast on Friday.
But I am warning you, it is very hacky... |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]