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)  Project design and development  Directory policy formed

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

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

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

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

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.

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 - address, URL White Pages Address Book LDAP query

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

Directory Uses – Authorization 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 Login server authN User Request Digital Service/Resource Directory

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

Directory Structure Tools  Registry: Oracle 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

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

Project Contacts  Paula Vaughan, Project Manager  Project Web Page or from the UCB - ITS home page: “About ITS”  “Projects & Initiatives”  “Architecture and Infrastructure Initiatives”