News

Open Sourcing Online ID Management

Redmond teams up with open source community to create an interoperable architecture for identity protection.

Microsoft has launched four new open source projects designed to implement information cards in a variety of formats, including Java, Tomcat (for IBM WebSphere servers), Ruby on Rails, PHP and a generic C library.

Redmond expects the results of these efforts to complement the ability of the Windows CardSpace identity-management system to support information cards.

The new projects will be hosted on two open source project sites: SourceForge and RubyForge. They'll also be aggregated at codeplex.com, Microsoft's collaborative development portal.

Information cards are the primary mechanisms for representing user identities in the so-called identity metasystem. The metasystem is an interoperable architecture for digital identity that assumes people will have several digital identities based on multiple underlying technologies, implementations and providers. The concept is the brainchild of Microsoft identity access architect Kim Cameron, who assembled the famous "7 Laws of Identity" in a white paper published about two years ago.

"It's a system of systems," explains Earl Perkins, research vice president at Gartner Inc. "A set of protocols for the exchange of personal identity information on the Internet. ... The idea is to provide an ecosystem that allows everyone to know who they're interacting with online."

The thing about the metasystem, says Thom Robbins, director of .NET platform product management at Microsoft, is that it's not a Microsoft-only environment. "So the interoperability pieces are key," he says. "We need to be able to work well with others and to take advantage of the common protocols."

People, Services and Providers
Three core elements make up the identity metasystem, explains Jean Paoli, Microsoft's general manager of interoperability and XML architecture: the people who are presenting their identity, the Web site or online service requesting proof of identity and the identity providers who assert some information about those people. The purpose of the newly launched projects is to improve interoperability for each of the identity metasystem components.

Paoli has been leading Microsoft's overall interoperability initiative for the past year. "Interoperability by design has four pillars," Paoli says. "We build interoperability into our products, we work on standards, we work with the community and we enable access to some of our technologies for the greater good, so to speak. These open source projects build on the last two."

The decision to open source the information card projects is Microsoft at its most pragmatic, Perkins observes. "It allows them to enlist, essentially, the whole world in making these connections," he says. "And it's good for Microsoft in another way: If these projects draw the kind of support they need from the open source community to be successful, it'll be a kind of tacit admission that Microsoft is now part of the open source world."

A Welcomed Effort
If the response from competing info card projects is any indication, Microsoft's prospects for success are good. In a Microsoft statement announcing the initiative, Paul Trevithick and Mary Ruddy, co-leads of the Eclipse Higgins Project, and Dale Olds, leader of Novell Inc.'s Bandit project, praised Redmond's efforts to increase the cross-platform interoperability of information cards. The Higgins Trust Framework Project, sponsored by The Eclipse Foundation, and the Bandit Project, sponsored by Novell, both seek to provide a consistent approach to managing digital ID information, regardless of the underlying technology.

"Microsoft's relationship with the open source community is complicated," says IDC's Mathew Lawton, program director for open source software business models. "Because they make a lot of money from proprietary software, everyone interprets that to mean that they're never going to do anything with open source software. But the company has demonstrated that it'll take advantage of the open source model when it helps them."

In a related announcement, Microsoft said that it plans to make its Identity Selector Interoperability Profile available under its Open Specification Promise (OSP). Last September, the company made 38 Web services specifications available under the OSP, which is Microsoft's public vow not to sue developers or customers for using designated technologies. With the addition of the Selector profile, an individual open source software developer or a commercial software developer can build its identity selector software and pay no licensing fees to Microsoft.

About the Author

John K. Waters is the editor in chief of a number of Converge360.com sites, with a focus on high-end development, AI and future tech. He's been writing about cutting-edge technologies and culture of Silicon Valley for more than two decades, and he's written more than a dozen books. He also co-scripted the documentary film Silicon Valley: A 100 Year Renaissance, which aired on PBS.  He can be reached at [email protected].

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