1 / 12

Directory Services Project

Directory Services Project. University of Colorado at Boulder. Directory Services - History. Project commission & goals articulated Project teams formed Requirements defined Interviewees (~40 campus representatives) Core Team (16 hands-on project team members)

nydia
Download Presentation

Directory Services Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. HR (fac/staff) SIS (student) FIS (faculty) Uniquid (accounts) Idcard (ISO) Telecom (where) Directory Goal:Trusted, authoritative data source CU Person

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

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

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

  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 Calendaring (winter, 2001) AD (future) Authentication (fall, 2001) Portals (future) White Pages (fall, 2001) email (future) manual input UCB Directory uccs Etc. ucd Telecom Registry Update uchsc FIS Directory Build Uniquid central SIS Identity Recon. H/R Recon report

  11. Project Contacts • Paula Vaughan, Project ManagerPaula.Vaughan@colorado.edu • Project Web Pagehttp://www.Colorado.EDU/committees/DirectoryServices/ or from the UCB - ITS home page:“About ITS” ž “Projects & Initiatives” ž “Architecture and Infrastructure Initiatives”

More Related