1. Directory Services Project University of Colorado at Boulder

2. Directory Services - History  Project commission & goals articulated  Project teams formed  Requirements defined Interviewees (~40 campus representatives) Core Team (16 hands-on project team members) Steering Team (6 university policy makers)  Project design and development  Directory policy formed

3. Directory Goal: Trusted, authoritative data source CU Person HR (fac/staff) SIS (student) Idcard (ISO) Telecom (where) FIS (faculty) Uniquid (accounts)

4. Directory Goal: Identity & relationship management CU UUID HR (EmpID) SIS (SID) Idcard (ISO) Telecom (tele#) FIS (SSN) Uniquid (unixID)

5. Directory Goal: Usable by applications & services Directory White Pages Active Dir. CalendarUPortalIDCard EMail Secure Netwkg

6. Directory Goals – Authentication Services 2. Authenticate (who), via ID & password, to trusted mechanism3. Determine Affiliation (what)4. Grant ticket/cookie (with who/what)5. Pass ticket to desired application1. Initial request. Redirect to authentication service6. Request add’l attributes as needed client Applications Directory trusted authN Authentication Services 1 2 3 4 5 6

7. Directory’s Trusted Data Goal and HR Personal data – demographic name, date of birth, gender Personal data – work-related employee ID, campus box, office phone, home department, original hire date Job data job code, department, business title, percent of time employment status, appointment end date

8. Directory’s Identity/Relationship Management Goal and HR Identifier matchers from HR:  Employee ID – already on file?  SSN – match with SIS student ID, previous ID?  Name – exact match or new?  Date of Birth & Gender – if no matching EmpID or SSN, then find matching name+dob+gender

9. Directory Uses of HR Data  SSN, name, gender and date of birth used to reconcile with SIS to ensure single directory entry per person.  Job status to determine active employment.  Job class code to determine type of employee.  Status plus job code to determine “affiliation” (and consequent directory listing and directory-authorized services).  Name, phone, campus box, title and department published in white pages.

10. Directory Structure Etc. Telecom FIS Uniquid SIS H/R Registry Update Directory Build uccs Calendaring (winter, 2001) White Pages (fall, 2001) Authentication (fall, 2001) email (future) Portals (future) ucd uchsc central UCB Directory Identity Recon. AD (future) manual input Recon report

11. Project Contacts  Paula Vaughan, Project Manager Paula.Vaughan@colorado.edu  Project Web Page http://www.Colorado.EDU/committees/DirectoryServices/ or from the UCB - ITS home page: “About ITS”  “Projects & Initiatives”  “Architecture and Infrastructure Initiatives”