LDAP-Enabled Privacy at The University of Notre Dame EduCAUSE conference, October 2002 Brendan Bellina Office of Information Technologies University of Notre Dame du Lac Copyright © Brendan Bellina, This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.

October, 2002Copyright © 2002, University of Notre Dame du Lac2 Confidentiality in U.S. Higher Education

October, 2002Copyright © 2002, University of Notre Dame du Lac3 Family Educational Rights and Privacy Act (FERPA) Institution definition of “Directory Information” –Full name –Address –Telephone number –Day and place of birth –College, major, or level –Participation in officially recognized activities and sports –Weight and height of members of athletic teams –Dates of attendance –Full or part-time status –Degrees and awards received –Most recent previous educational agency or institution attended by the student –Other similar information such as a photograph

October, 2002Copyright © 2002, University of Notre Dame du Lac4 Family Educational Rights and Privacy Act (FERPA) Publish Official Request Process: Notre Dame’s process requires that the student must file written notification that he/she wishes to prevent disclosure of the designated directory information with the Registrar’s Office.

October, 2002Copyright © 2002, University of Notre Dame du Lac5 Initiating FERPA Protection: The Student Request FERPA protection at registration or… Submit formal request for FERPA protection to the Office of the Registrar providing name and/or login id Wait for request to be processed.

October, 2002Copyright © 2002, University of Notre Dame du Lac6 Initiating FERPA Protection: The Office of the Registrar Update Student Information System record to indicate that the student has requested FERPA protection Contact the Office of Information Technologies to have electronic directories & services updated

October, 2002Copyright © 2002, University of Notre Dame du Lac7 Limitations Complex and slow– multiple steps and points of failure and delay Available only during office hours M-F 8-5 Cumbersome – requires student visit Dependent on availability of system administrators for multiple systems (core middleware, ) Limited granularity – phone, address, spouse name, or all

October, 2002Copyright © 2002, University of Notre Dame du Lac8 Unwanted Side Effects Disabled functions reliant upon ph entry information, including forwarding and WebCT Created errors during listserv processing Required coding modifications for each request Required configuration modifications for each request Separated user account from source systems, preventing automated disablement

October, 2002Copyright © 2002, University of Notre Dame du Lac9 Goals Self-service web application Multi-level opt-out Automate processes Reduce administrator involvement Eliminate need for coding and configuration changes 7x24x365 availability Immediate effect – no latency Attribute level granularity Eliminate need for office visit No restrictions on services caused by privacy

October, 2002Copyright © 2002, University of Notre Dame du Lac10 Steps Taken to Date Script written to perform several of the administrator functions Implementation of Enterprise Directory Service with redundant iPlanet LDAP Sun E250 Servers Elimination of X.500 directories and Eudora ndbm database to further reduce administrator involvement

October, 2002Copyright © 2002, University of Notre Dame du Lac11 Steps Taken to Date Web pages implemented to allow user to edit entry content and update privacy options in the Enterprise Directory Service real-time, 7x24x365. Provide LDAP-enabled applications with service id’s authorized to access private entries Windows Active Directory domain policy to redirect Active Directory searches to the EDS

October, 2002Copyright © 2002, University of Notre Dame du Lac12 Screen Samples

October, 2002Copyright © 2002, University of Notre Dame du Lac13 EDS Authentication Screen

October, 2002Copyright © 2002, University of Notre Dame du Lac14 Directory Entry Display

October, 2002Copyright © 2002, University of Notre Dame du Lac15 Directory Entry Edit

October, 2002Copyright © 2002, University of Notre Dame du Lac16 Privacy Options

October, 2002Copyright © 2002, University of Notre Dame du Lac17 Display Preferences

October, 2002Copyright © 2002, University of Notre Dame du Lac18 Opt-out Options Entry level and Attribute Level –Private – The entry/attribute is visible only to the owner and to authorized applications. This is a selectable option for active student and departmental accounts. –ND-Only – The entry/attribute is visible to authenticated searches and to authorized applications. This is a selectable option for all active accounts.

October, 2002Copyright © 2002, University of Notre Dame du Lac19 How It Works

October, 2002Copyright © 2002, University of Notre Dame du Lac20 Directory Attributes: dn Directory dn is comprised of: –ndGuid – a uniquely defined string of characters derived in part from University id –Directory base Intentionally avoided basing on name or login id in order to: –(1) reduce chance of dn changes when name changes occur, and –(2) allow anonymity without requiring entire entry to be restricted.

October, 2002Copyright © 2002, University of Notre Dame du Lac21 Directory Attributes: ndEntryStatus Multi-valued attribute used to control access to the entry from applications. Allowable values: –active –restrictEDS – indicates entry restricted to owner and authorized applications –restrictndonly – indicates entry restricted to authenticated searches

October, 2002Copyright © 2002, University of Notre Dame du Lac22 Directory Attributes: ndVisibilityControl Multi-valued attribute used to record access level for specific attributes Allowable values: Attribute name, + –private – indicates attribute restricted to owner and authorized applications –ndonly – indicates attribute restricted to authenticated searches

October, 2002Copyright © 2002, University of Notre Dame du Lac23 Directory Attributes: ndDisplayPreferences Multi-valued attribute used to record user preferences for the directory entry display screen Allowable values: –maskpriorsurname – indicates that common name values based on prior surname should not be displayed –maskuid – indicates that uid (login is) should not be displayed

October, 2002Copyright © 2002, University of Notre Dame du Lac24 Directory Attributes: aci Entry level aci’s used to control access to entry attributes as specified in ndVisibilityControl Ou level aci’s used to prevent unauthorized access to restricted attributes such as ndUniversityid, ndPermid, ndRolesAssigned

October, 2002Copyright © 2002, University of Notre Dame du Lac25 Directory Attribute Access Types Always restricted –exp. ndUniversityid, ndPermid, ndRolesAssigned Never restricted –exp. dn, uid Restrictions based on user preference

October, 2002Copyright © 2002, University of Notre Dame du Lac26 Directory Attribute Access Groups Groups are used to allow applications to have access to entries and attributes. Use of groups reduces directory maintenance/administrative time Groups are not visible anonymously

October, 2002Copyright © 2002, University of Notre Dame du Lac27 Steps Remaining Elimination of public access to ph Inclusion of FERPA opt-outs in the EDS Implement a tie between the EDS opt-out and FERPA settings and Registrar notification

Links ND Enterprise Directory Service, ND EDS Documentation, ND EDS Schema Documentation, ND EDS Search, eduPerson object class, Internet2,

Contact Information Brendan Bellina Office of Information Technologies University of Notre Dame du Lac Website: Directory Entry: vCard: