Share via

Have you Climbed up Zermatt Yet?

  • Article

ZermattSo a month ago we announced the "Zermatt" Developer Framework which as an SDK which aids developers to build claims based aware applications that support the Identity Meta System ( through WS-* protocols). So far it has gotten a lot of interest and I wanted to reiterate the potential here and make sure that you give it a try ( kick the tires as to speak).

Ultimately developers can build externalized authentication capabilities for “relying party” applications and build custom “identity providers”, often referred to as Security Token Services (STS).  With these components, developers can build applications that meet a variety of business needs more quickly

The industry-wide vision for an Identity Metasystem is gaining traction.  Key to this vision is the externalization of authentication from applications and enabling user access based on claims.  Today developers must choose between numerous identity technologies for different application scenarios (e.g., X.509, Kerberos, LDAP) and custom identity logic is required to be built into each application for many scenarios, and custom integration is required for deployment.  This results in numerous application silos that are inflexible, costly and difficult to evolve.

This is the beauty of the what is being provided here is that with these components, developers can build applications that meet a variety of business needs more quickly and get to choose the technology deployment down the line.

Details

Link to the beta:  https://go.microsoft.com/fwlink/?LinkId=122266

Whitepaper:  https://go.microsoft.com/fwlink/?LinkId=122266 or located here on idaweb

Requirements:  “Zermatt” requires .Net 3.5 to be installed. It has been verified on Windows 2K3 SP2 with IIS 6.0 and Windows Vista SP1 and Windows Server 2008 with IIS 7.0.  The final list of supported platforms for the RTM version of Zermatt has not yet been announced.

Roadmap:  We anticipate RTM to occur in the last quarter of calendar year 2008. 

More info on MSDN:  https://msdn.microsoft.com/en-us/security/aa570351.aspx

Comments