Microsoft Identity Integration Server

Microsoft identity integration server (MIIS) is an identity management (IdM) product offered by Microsoft. It is a service that aggregates identity-related information from multiple data-sources. The goal of MIIS is to provide organizations with a unified view of a user's/resources identity across the heterogeneous enterprise and provide methods to automate routine tasks.

Microsoft identity integration server manages information by retrieving identity information from the connected data sources and storing the information in the connector space as connector space objects or CS Entry objects. The CS Entry objects are then mapped to entries in the metaverse called metaverse objects or MV Entry objects. This architecture allows data from dissimilar connected data sources to be mapped to the same MV Entry object. All back-end data is stored in Microsoft SQL Server.

Product evaluation documentation:

☛ Classic Metadirectory Walkthrough

☛ Simple Account Provisioning Walkthrough

☛ Global Address List Synchronization Walkthrough

☛ Group Creation and Provisioning Walkthrough

☛ Password Management Walkthrough

Example:

Through the metaverse an organization's e-mail system can be linked to its human resources database to the organization's PBX system to any other data repository containing relevant user information. Each employee's attributes from the e-mail system and the human resources database are imported into the connector space through respective management agents. The e-mail system can then link to individual attributes from the employee entry, such as the employee telephone number. If an employee's telephone number changes, the new telephone number will automatically be propagated to the e-mail system.

Versions of microsoft identity integration server:

☛ Zoomit Via (pre 1999)

☛ Microsoft Metadirectory Server [MMS] (1999-2003)

☛ Microsoft Identity Integration Server 2003 Enterprise Edition [MIIS] (Retired)

☛ Microsoft Identity Integration Server 2003 Feature Pack [IIFP] (Retired)

☛ Microsoft Identity Lifecycle Manager Server 2007 ILM (Retired)

☛ Microsoft Forefront Identity Manager 2010 FIM (Current)

The microsoft identity integration server is extensible through the use of the .NET framework, which allows developers and network administrators to extend out of the box capabilities and perform complex tasks.

The goal of the fictional scenario and walkthrough described here is to ensure that all of the directory information maintained in a number of diverse, separate systems is synchronized and that the information is correct. This scenario and walkthrough describes how to build a Microsoft Identity Integration Server 2003 (MIIS 2003) infrastructure that will make the identity information in these diverse data sources consistent throughout an enterprise.

Before beginning this scenario, become familiar with the basic concepts of MIIS 2003. In This Walkthrough:

☛ Scenario Design

☛ Lab Setup

☛ Implementation Steps

☛ Administering MIIS 2003 Infrastructure

Scenario design describes the fictional company and the specific directory problem you solve in the scenario. This section provides a high-level conceptual and procedural overview of how MIIS 2003 facilitates data flow between connected data sources and Microsoft Identity Integration Server 2003.

This documentation set includes walkthroughs that help you with proof of concepts and detailed analyses of features and functionalities of MIIS 2003. You also get information that helps you make business cases when choosing MIIS 2003.

Implementation steps provides a procedural walkthrough for building the MIIS 2003 management agents (MAs) used to develop the MIIS 2003 infrastructure in the scenario.

Lab setup lists the hardware and software requirements for the scenario walkthrough procedures. Includes detailed instructions for setting up the different connected data sources, as well as setting up MIIS 2003.

Administering MIIS 2003 Infrastructure provides common administrative tasks related to maintaining the MIIS 2003 infrastructure in the scenario.

The following software should be available:

☛ Windows Server 2003, Enterprise Edition

☛ Microsoft Identity Integration Server 2003

You will create the MAs in the following order:

☛ HR MA

☛ LDAP Data Interchange Format (LDIF) MA

☛ AD MA

☛ Sun ONE Directory Server 5.1 MA

☛ Telephone MA

To administer the Microsoft Identity Integration Server 2003 infrastructure, perform the following administration tasks:

☛ Connect connector space objects to the metaverse, which includes:

1. Attribute indexing

2. Connecting disconnector objects

3. Disconnecting connector objects

4. Previewing action on disconnector objects

☛ Manage management agents

☛ Create command scripts for management agents

☛ Use administrative roles

Integration Server (MIIS) 2003 allows you to synchronize identity information from many different directories and services into a single, organization-wide solution. This can help protect your network's security and simplify management.

Some of the major capabilities of MIIS 2003 include:

☛ Directory synchronization

☛ Account provisioning

☛ Certificate publishing

☛ Group management

☛ Management of Global Address Lists (GALs) for diverse e-mail systems

☛ Management and synchronization of passwords