1. Enterprise Directory Services A Common Registry (Identity Management) & Common Source of Authoritative Attributes Presentation to the Office of the President (4/26/02)

2. Project Goals Provide a common source of identity information for persons associated with the University.Provide a common source of identity information for persons associated with the University. Enable the implementation of the New Business Architecture.Enable the implementation of the New Business Architecture. Enable collaboration among the campuses of the University of California.Enable collaboration among the campuses of the University of California. Improve the campus system security architectureImprove the campus system security architecture Enable data warehousing.Enable data warehousing.

3. Progress Advanced Technology ProjectAdvanced Technology Project –Completed March 2001 and involved significant collaboration within the campus –Investigation of campus needs –Possibilities for the architecture –Schema considerations Project Charge to Develop Enterprise Directory Services for the CampusProject Charge to Develop Enterprise Directory Services for the Campus Pre-Feasibility Analysis and Project Work planPre-Feasibility Analysis and Project Work plan

4. Proposed Enterprise Directory Services PropertiesProperties –A Common Identity Management (Person Registry) and Common Authoritative Attributes (LDAP Directory) –Applications are Directory Enabled and Read and Write to an LDAP directory –Eliminates Need for Extraction from multiple Source Data Repositories

6. The Person Registry Key to Success A central database of identity information for all persons within the University CommunityA central database of identity information for all persons within the University Community Creates a Unique ID for every person for whom a computer record is generated. The Unique ID follows that person from “cradle to grave”.Creates a Unique ID for every person for whom a computer record is generated. The Unique ID follows that person from “cradle to grave”. Establishes a resolution process to insure unambiguous and accurate records.Establishes a resolution process to insure unambiguous and accurate records. Campus computing systems adopt the Unique ID to identify that person in the system.Campus computing systems adopt the Unique ID to identify that person in the system.

7. Person Registry (Common Identity Management)

8. Directory Services Once Registry processes for creation and maintenance of the Unique ID are adopted, we have many options for creating and configuring directory services.Once Registry processes for creation and maintenance of the Unique ID are adopted, we have many options for creating and configuring directory services. –Central System Architecture –Referral System Architecture –Chained System Architecture – etc...

9. Possible Directory Models

10. Pre-Feasibility Analysis

11. Discussion Points Can we collectively achieve UC-wide unique identities?Can we collectively achieve UC-wide unique identities? How will we integrate the middleware components and business applications into the New Business Architecture?How will we integrate the middleware components and business applications into the New Business Architecture? Will UC maintain a Directory of Directories for our campuses?Will UC maintain a Directory of Directories for our campuses? How will we resolve inter-realm (UC-wide) authentication and authorization?How will we resolve inter-realm (UC-wide) authentication and authorization? Are there opportunities for UC Davis and Office of the President to work together to address identity issues?Are there opportunities for UC Davis and Office of the President to work together to address identity issues?