1 / 14

UCB Enterprise Directory Services

UCB Enterprise Directory Services. Directory Services – Project History. Requirements defined Project commission & goals articulated Project teams formed Interviewees (~40 campus representatives) Core Team (16 hands-on project team members) Steering Team (7 university policy makers)

tadhg
Télécharger la présentation

UCB Enterprise Directory Services

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. UCB Enterprise Directory Services

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

  3. HR fac/staff; empID SIS student; SID FIS faculty; SSN Uniquid accounts; unix ID IDcard photos; ISO Telecom phone locn phone # Directory Goals • Trusted and authoritative data source • Identity and relationship management • Usable by applications and services CU Person

  4. SIS Directory Student Data For Identity Matching: - Student ID - Birth date - Gender For Data Access - Privacy Flag For Directory Publication - Name - Local Address and Telephone - Major(s) and Minor(s) - College(s) - Class Level

  5. HR Directory Faculty and Staff Data For Identity Matching: - Employee Number - SSN - Birth date - Gender For Job Selection - Job status - Employment end date For Directory Publication - Name - Campus Box and Phone - JobDepartment(s), Home Department - Job ClassTitle(s) - Business Title(s)

  6. Uniquid Account & Email data ID Card ISO and jpeg Telecom Office building/room data FIS Faculty Research and Degree data Campus-Specific Data or Systems Directory

  7. Directory Uses of Data • SSN, name, gender and date of birth used to reconcile between SIS and HR. • Job status and appointment end date used to determine active employment. • Enrollment status, expected return date and withdraw code used to determine active student. • Academic Unit and/or Job Code used to determine “affiliation” (faculty, staff, student, member, affiliate) – and consequent directory listing and directory-authorized services.

  8. White Pages LDAP query Address Book Directory Uses – Anonymous Queries Directory • “Directory” (public) data: • -Search based on name • Students without privacy flags • All faculty/staff • Student local phone/address • Faculty/staff office phone/address • Student major, minor, college, class • Faculty/staff title, department • Email address, URL

  9. Directory Uses – Applications Directory Calendar • Directory and application extensions: • - Authenticated application • - Access to directory based on application rights • Use standard directory attributes (name, email) • Extend directory attributes (preferences) • Use application-specific attributes (schedule)

  10. User Request Digital Service/Resource authN Login server Directory Uses – Authorization Directory • Directory and authorization for services/resources: • - Request resource • - Authenticate (you are who you say you are) • - Authorize (you can do what you want to do) • - Determine affiliation (faculty, staff, student, etc.) • Pass affiliation to requested service/resource • Pass additional attributes as needed by application

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

  12. Directory Structure Tools • Registry: Oracle 8.1.7.1 database • Directory: iPlanet v5 directory server • SIS and Uniquid Data Extracts: Java • HR Extract: SQL calls through DB Link to the PS Reporting database • Registry update process logic: PL/SQL • Directory load process: Metamerge • White pages application: Cocoon running on Apache and Tomcat

  13. Directory Policy • Scope: enterprise, blending of systems • Governance guidelines: collaborative representation • Inclusion guidelines: University affiliates from systems of record and sponsorship • Entry guidelines: authenticated systems and users • Use guidelines: privacy regulations, access controls, directory-enabled systems • Procedures: regular policy review, compliance through ITS, CIO and Directory Governance Board

  14. 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