These documents were written to guide the work of the MCommunity system developers, although others might also find them interesting. Each chapter lists requirements for a different component of the MCommunity system. Each chapter is a separate document.
The MCommunity enterprise directory system is made up of the following logical components:
Identity Management. A comprehensive set of tools and processes for creating and managing digital identities for all entities that are affiliated in some capacity with U-M and that need access to IT resources.
Sponsor System. An interface to the identity management system that allows authorized people and processes to perform additions and modifications of/to identity data for persons loosely affiliated with the University.
Identity Vault. This includes the Registry and Directory, which serve as the data and processing hub for identity management, service provisioning, and workflow. The modules of the Identity Vault subsystem are:
Registry. The restricted-access collection point for person identity data from institutional sources (such as human resources, student, and development systems), including the Sponsor System. It is the point of all person identity creation.
Directory. An accessible directory that contains active person and non-person identity data, roles, and groups for the purpose of provisioning IT resources.
LDAP Tree. An LDAP-accessible directory instance. We are also including here the requirements for the components of MCommunity that support the ID Vault, such as the User Applications and Workflow.
Roles System. System consisting of role objects in the Directory and processing logic to associate identities to them based on defined rules for membership. Based on these roles users will be granted and denied access to IT resources.
Provisioning. A set of tools that allows different constituencies at the university to use directory identity information to authorize use of the local resources.
Audit System. All events relevant to identity management and service provisioning that warrant long term tracking will be recorded in an audit system capable of storing, normalizing and reporting on these events.
