O'Reilly logo

A Guide to Claims-Based Identity and Access Control by Eugenio Pace, Matias Woloski, Keith Brown, Vittorio Bertocci, Dominick Baier

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Chapter 5. Federated Identity for Web Services

In Chapter 4, you saw Adatum make the a-Order application available to its partner Litware. Rick, a salesman from Litware, used his local credentials to log on to the a-Order Web site, which was hosted on Adatum’s domain.

To do this, Rick only needed a browser to access the a-Order Web site. But what would happen if the request came from an application other than a Web browser? What if the information supplied by aOrder was going to be integrated into one of Litware’s in-house applications?

Federated identity with an active (or “smart”) client application works differently than federated identity with a Web browser. In a browser-based scenario, the Web application requests security tokens by redirecting ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required