InfoQ

News

Microsoft announces release of “Zermatt” Identity Framework

Posted by Dilip Krishnan on Jul 23, 2008 03:03 PM

Community
.NET,
SOA
Topics
Web Services ,
Security ,
.NET Framework ,
WS Standards
Tags
SOA Appliance ,
WS-Trust ,
WS-Policy ,
WS-Security ,
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.

No comments

Watch Thread Reply

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.