News

Google, Microsoft, IBM, VeriSign and Yahoo Join OpenID Board

In a move that could help deliver single sign-on to the masses, Google, Microsoft, IBM, VeriSign and Yahoo have joined a consortium that backs a common federated identity specification.

The vendors jointly announced their membership to the OpenID Foundation's board on Thursday, Feb. 7. The OpenID spec allows individuals to create one user name, password and other credentials for logging onto multiple Web sites that support the spec.

"It's a really easy way for users to be able to secure their identities," said Scott Kveton, vice president of open platforms at Tulsa-based Vidoop LLC, a supplier of multi-factor security software. Kveton, who is chairman of the OpenID community board, said corporate developers can also incorporate the spec into their applications.

"When you think of OpenID, it's a very open, public-facing kind of technology, but you can also run an OpenID provider for use inside of your firewall," Kveton said, adding there are implementations available in multiple programming languages and environments, including Java, .NET, Python and PHP.

Microsoft Chairman Bill Gates and Chief Research and Strategy Officer Craig Mundie first announced support for the spec exactly a year ago at the 2007 RSA Security conference when Microsoft, JanRain, Sxip and Verisign said that they would work together to provide interoperability between OpenID and Windows CardSpaces.

The problem is that such an implementation will presume developers are working with the .NET 3.0 Framework, which, for now, is only a small percentage of the overall Windows developer community, said Jeffrey McManus, principal of San Francisco consulting firm Platform Associates.

"It seems like a pity it would require someone to have to wait a year or two until an organization adopts a later version of the .NET stack to be able to adopt OpenID," McManus commented. However, he points out that there are some third-party tools that allow developers to use older versions of the .NET stack. One from ExtremeSwank was updated last week.

OpenID is a community-developed and maintained spec, though the foundation is not operating as a formal standards-making body. "It's a good example of community-driven standards verses a vendor-driven standard," McManus said.

Kveton said there are no plans for the group to become a standards body or to do certification, but it hasn't ruled out conducting interoperability tests.

Microsoft's representative to the OpenID board is Mike Jones. "The Internet is still missing a much-needed ubiquitous identity layer," Jones wrote on his blog. "The good news is that the broad industry collaboration that has emerged around OpenID is a key enabler for building it together."

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube