InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Microsoft announces release of “Zermatt” Identity Framework

Posted by Dilip Krishnan on Jul 23, 2008

Sections
Architecture & Design,
Development,
Enterprise Architecture
Topics
Web Services ,
WS Standards ,
SOA ,
.NET Framework ,
.NET ,
Security
Tags
WS-Trust ,
WS-Security ,
WS-Policy ,
SOA Appliance ,
WS-MetadataExchange

Microsoft released a beta of “Zermatt”, an identity framework for developers using the .Net framework. The framework helps developers build claims-aware applications to address application security requirements using a simplified application access model.

According to Kim Cameron, Chief Architect of Identity in the Connected Systems Division at Microsoft, the framework makes it easy to do the following

Building claims-aware applications

Zermatt makes it easier to build identity aware applications. In addition to providing a new claims model, it provides applications with a rich set of API’s to reason about the identity of a caller using claims.

Zermatt also provides developers with a consistent programming experience whether they choose to build their applications in ASP.NET or in WCF environments. 

Building Security Token Services (STS)

Zermatt makes it substantially easier for building a custom security token service (STS) that supports the WS-Trust protocol. These STS’s are also referred to as an Active STS.

In addition, the framework also provides support for building STS’s that support WS-Federation to enable web browser clients. These STS’s are also referred to as a Passive STS.

Creating Information Cards

Zermatt includes classes that you can use to create Information Cards - as well as STS’s that support them.

The framework builds on several WS-* standards like WS-MetadataExchange, WS-Policy, WS-Trust etc. and uses Windows CardSpace. The framework is interoperable with other popular web service stacks and also comes with UI widgets and a plumbing to make developing secure single-sign-on applications in ASP.net very simple.

More information is available in the developer white paper on "Zermatt" written by Keith Brown who says that "All you need to test-drive Zermatt is Visual Studio 2008 and your curiosity".

Other great resources to follow "Zermatt" and other identity related developements are Vittorio Bertocci and Kim Cameron's blogs.

  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

Educational Content

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.