Microsoft Healthvault doesn’t really support OpenID. I suppose this shouldn’t be all that surprising, but they do feature the logo and claim to…
I entered my usual id. They told me to use a https url (guys, http auth can be encrypted – don’t judge my endpoint, or the URL from which I delegate). I went and found the google OpenID url (https://www.google.com/accounts/o8/id), and was told it wasn’t an OpenID 2.0 url. I went and found the OTHER one (the same URL as my google profile). This FINALLY prompted a message that informed me that they didn’t, in fact, support any providers other than this very short list:
- pip.verisignlabs.com
- openid.trustbearer.com
- myopenid.com
- myvidoop.com
Really? you support myvidoop.com and verisign’s beta implementation, but not Google? Good going, Microsoft. If the supported list is that short, you should just show provider logos and forgo the “enter url” box. At the very least, show me that list BEFORE I try to log in.
I don’t really want a Live account. It appears I need one to use the service with which my health provider has chosen to partner. Bother.
Post a Comment