Assurances in Identity

Michael Wittenburg, a colleague with MCS - UK, recently sent through a link to a case study of a project I was involved in with him. The Internet Access to Shared Service (IASS) project aimed to provide the UK Ministry of Defence with secure remote access to its line-of-business applications . You can find the case study here: Case Study - The Ministry of Defence . The IASS solution used combination of multiple products to enable the secure remote access, including: Microsoft Active Directory Directory Services Microsoft Intelligent Application Gateway (IAG) Microsoft .NET Framework Microsoft BizTalk Server 2006 Microsoft Identity Lifecycle Manager 2007 FP1 (ILM) Microsoft Internet Security and Acceleration Server 2006 Gemalto Chip & PIN (EMV) .Net Smart cards I spent quite a few weeks at the Microsoft Technolo

ILM 2007, through its Certificate Management solution, or Certificate Lifecycle Manager (CLM) as it used to be known, allows an organization to manage credentials within their Windows Server 2003 and 2008 certification authorities. It acts like an administrative proxy, allowing you issue and manage digital certificates and smartcards through a web interface. The solution provides three different APIs (i.e. Provision, SQL and Notification) and a number of customizable interfaces, all of which allow you to customize CLM. This gives you the ability to greatly extend and expand the product's capabilities. For an overview of these APIs and interfaces, have a look at the Certificate Lifecycle Manager Overview on MSDN. Over the next few postings, I'll be looking at these APIs and interfaces in greater detail, to show you how they work and how they could be put to use in your CLM deployment. And I'd like to add a quick shout-out to David Lundell, over at ILM Best Practices , f