A few postings, here, here and here already talk about converting their blog urls into OpenID URLs. This method allows you to use your blog URI as your OpenID URI and login any one of the participating websites using that, as opposed to creating yet another user account on that website.
Those who already have an i-name (mine is http://xri.net/=rajeev.karamchedu) can use that instead. If you truly want a single URI, then why use a blog address ? The blog address is not permanent either. So instead of using the blog address, I created a forwarding service in my iname called (+openid) that will take me to my real open id
So my openid now is http://xri.net/=rajeev.karamchedu/(+openid)
A typical login process on a website then becomes:
- Supply your OpenID as http://xri.net/=<your iname>/(+openid) on the website (e.g. example.com)
- XRI.NET is contacted for a forwarding service, which then forwards to your OpenID server
- OpenID server authenticates example.com allowing you to control the duration of this authentication.
Using such an example, one can see that i-name framework complementing that of the OpenID. The thing that is bad about it is that I still have to create TWO accounts: One with the i-name service provider and another with an OpenID provider.
Can they not be the same ?
[...] if OpenID does become the de factor public identifier, i-names would be an apt running mate. Tagged with: i-names, openid, public identifier standard, XRI « How should we handle [...]
Yes you did and I had more related questions here as well. To repeat:
Given a list of openid enabled websites – are ALL of them running OpenID 2.0 ? Don’t think so, cause there is at least 1 site I know of that failed my native openid login request but worked with the URI request.
=rajeev
oops, the greater than and less than brackets got lost… what that was meant to say was.. “You can type ‘your i-name’ into any OpenID 2.0 login box and it will all ‘just work’.
Rajeev, I answered this one right? Your i-name DOES resolve, using XRI resolution to an openID service. You don’t NEED the http://xri.net/=/(+openid) stuff. You can type into any OpenID 2.0 login box and it will all ‘just work’. It is mandated by XDI.org, the governing body of the i-name space, that all global names automatically have openID services associated with them. Our community name services also provide all community i-names openID services as well.
We good on this one?
Thx for your note, Gabe.
Then there is this matter of multiple i-brokers. I noticed that these brokers don’t talk to each other. Two user accounts and passwords on two websites …clearly not eating their own dog food… :)
They could be the same if your i-broker made it possible. I’d suggest you send them an email referring to this blog entry and you may find them being quite accommodating.