1. Middleware & Enterprise Services at College Park David Henry Office of Information Technology dhenry@umd.edu November 16, 2001

2. Current State WAM Glue umail Dial-up DHCP LAN Other Systems ARES Testudo UMEG Web pages CorporateTime accmail Deans UNIX ClusterWebCT Meeting MakerGroupwise NotesBlackboard

3. User Interface - Portal Where we want to be Applications - email, HR, SIS, FRS, WebCT, etc. Application Infrastructure -user mgmt, security, directory, authorization, authentication System & Network Infrastructure

4. Establishing the Infrastructure Construct a Directory (LDAP) Establish a common user name space Policies on membership/roles Processes for managing data & information Use existing systems/data wherever possible

5. What the “I” will provide Single sign-on Common access via web portal Common and consistent (standards-based) mechanism for authentication and authorization 24X7 services Ability to use freely available access tools Don’t need special client tools (e.g. Oracle) Many COTS packages contain hooks for LDAP already!

6. Constituencies/Roles –Prospective students –Students –Faculty (current and Emeritus) –Staff –Affiliates ( Visiting faculty, Golden ID, etc.) –Alumni

7. Universal Login ID Today there are too many ids –WAM ID, Glue ID, umail ID, UMID, SID, etc. UMID/SID both very like the SSN We want to stop using the SSN The directory provides a character based ID (e.g. dhenry, drriley) Apps that now use UMID/SID should be enabled to use Directory ID

8. Universal Login ID - UMID Redefine UMID to mean the character based id and NOT the 9-digit number All apps reference UMID (meaning character based id) Some apps would support both for some time (e.g. ARES, Testudo) One app requires numeric ID (i.e.MARS) –Still used by about 20% of students The UMID becomes the Universal Login ID

9. Some Directory enabled apps Email –On-the-fly directory searches for email addresses –Central forwarding (name@umd.edu) CorporateTime scheduling software Web sites –OIT Staff Listing –Letters & Sciences Advising schedules –Physics course evaluation WebCT www.courses.umd.edu

10. More Directory Enabled Apps Portal Dial Up access DHCP registration Wall jack registration in Residence Halls Card key systems More…

11. Security Services PKI requires a directory for publication of the public key –See www.oit.umd.edu/middleware/PKI Encrypted documents/email Signed documents Secured access to web servers

12. USM Initiative Goal is to establish overarching directory for USM –Identification only, no authn, not another userid PeopleSoft as an “opportunity” –BPR –directory tie-in –Possible to select new identity value –We want to be sure what is done today better prepares for USM directory in the future Uses? –Library patron authorization –Shady Grove and other similar things –People with relationships w/multiple USM Institutions

13. Enterprise Services CorporateTime –~3000 accounts, used by >200 units Electronic Mail Consolidation Initiative –Preparing RFP now Bulk Email Service –Mail to College, Dept, majors, course, class, section - by authorized persons –Tie in to Advise for special mail lists

14. Portal Project E-Maryland Portal RH Smith Portal prototype University Portal –Overview www.oit.umd.edu/portal –Planning underway –Established Portal Advisory Committee –Developing requirements & specifications –Lots of user input from most constituencies

15. That’s IT David Henry OIT University of Maryland