The technical white paper, entitled "Identity Systems and Liberty Specification version 1.1 Interoperability," compares and contrasts the consortium's federated identity model against .Net Passport, Verified by Visa, and other third-party authentication systems.
The paper was produced to address questions and misconceptions about the Liberty Alliance model, said Paul Madsen, the paper's author and a consultant in the Advanced Security Technologies group at Entrust.
"The paper was motivated less to define a framework for
In particular, the paper was written to address the misconception that
While it may be fair to compare Passport to a particular implementation of the
For example, The Liberty Alliance specifications back the use of Security Assertion Markup Language (SAML) for exchanging authentication tokens as compared with Passport's proprietary schema, and the two authentication systems differ in the way they communicate tokens from one site to the next.
"There were a lot of misconceptions about how
On that score, the new white paper proposes a number of scenarios in which .Net Passport and
In one scenario, a third-party Web site might act as an identity provider in a Liberty "circle of trust" (COT), creating SAML assertions for other service providers while also existing as a Passport member site, processing tokens issued by Passport.com.
In this scenario, Identity.com would then act as a "mediator" between the Liberty-governed domain and the Passport domain, converting Passport tickets into SAML assertions and vice versa.