Yahoo! released its Browser-based authentication (BBAuth) mechanism yesterday. It can be used to authenticate 3rd party webapp users to Yahoo!â€™s services, for example, photo sharing, email sharing.
Big deal, huh?
The kicker is this though. You can use BBAuth for simple single sign-on (SSO). Most 3rd party web app developers would love to have someone deal with the username and password issues. Not storing usersâ€™ passwords mean much less liability, much less programming, much less problem.
Now Yahoo! gives you a REST-based API to do just that.
It will be interesting to see how this plays out against OpenID.They are both very similar. Granted there is some skew: OpenID is completely open, both for consumers and providers of identity.
However, from my own experience, OpenID consumers (a.k.a. relying parties) seem to want only one thing, perhaps two or three:
- have someone deal with your usersâ€™ passwords,
- retrieve name and email address for a user
And now Yahoo! does the first, and the second is available. At the same time theyâ€™re making your app reachable to 257 million+ users. Hereâ€™s an example.
Seems a pretty big reason to implement it for the web app developer, especially since it is such an easy API you can integrate it in an hour or two.
And yet someone has added a sobering comment to Hans’ blog:
It will be interesting to see how long it takes for adoption to reach the point that no one thinks twice when a yahoo login pops up on another site. They'll be nice and ripe for password harvesting via fake yahoo login forms then.
Sadly, if I had written this comment I would not have included the happy face. Until the security concerns are addressed, despite Yahoo's very laudible openness, this is not a happy face moment.
But through Yahoo-issued InfoCards BBauth would avoid the loss of context that will otherwise lead to password harvesting. It's a good concrete example of how the various things we're all working on are synergistic if we combine them.