USM Middleware Workgroup
Key Steps to Implement Directory Services
- Define the objective for your Directory Service.
- Get buy-in and support from senior administration. Try to get
a VP-level administrator as the project champion.
- Analyze the applications that will be your data feeds and the
systems that will interface with the directory.
- Get approval from appropriate data owners.
- Decide on the GUID to be used to access records in the
globally unique identifier. SSN's were commonly used in
the past and should not be used.)
- Design a registry system for people data. This is the
process of assigning each faculty, staff, student, and
affiliates a unique identifier in the system. The most
common approach is to use a database like Oracle to merge
data together and assign unique IDs.
- Decide on an authentication mechanism. Passwords are
- Develop the schema for your identified data fields.
inetOrgPerson and eduPerson should be used as well as a
MYORG_eduPerson for locally defined data.
- Use the already available USM OID or apply for an OID
from IANA www.ianna.org.
Develop an OID assignment table. Available USM OID
assignments are as follows:
19212.00 System-wide Objects
19212.01 University of Maryland, College Park
19212.02 University of Maryland, Baltimore
19212.03 University of Maryland Biotechnology Institute
19212.04 University of Maryland Eastern Shore
19212.05 University of Maryland, Baltimore County
19212.06 University of Maryland University College
19212.07 University of Maryland Center for
19212.08 University System of Maryland Office
19212.09 Bowie State University
19212.10 Coppin State College
19212.11 Frostburg State University
19212.12 Salisbury University
19212.13 Towson University
19212.14 University of Baltimore
- Design the physical infrastructure. The design should
take into account redundancy and the need for 24x7 uptime.
- Decide on LDAP server software. Some of the most common
servers are: Novell eDirectory, SunOne Directory, LDAP,
MS Active Directory server, IBM Secureway LDAP
- Setup physical hardware and software for the LDAP server.
- Design the LDAP structure. Design should be very flat
and should contain a People OU and make use of Domain
- Example: OU=People, DC=umaryland, DC=edu
- Extend the schema to include: inetOrgPerson,
- Develop connectors or data load programs and decide
on frequency of updates.
- Develop policies on the following:
- Who can access what data?
- How often will data be updated?
- What sources are authoritative and what data sources
are to be updated?
- What data will be stored in the directory? What are
- Will data be accessed securely or in clear text?
- What is the policy on passwords? Format? Expiration?
- Develop/modify applications in a test environment.
- Test! Go live!
Important reference information on
developing middleware in the higher education environment:
Metadirectory Practices for Enterprise Directories
in Higher Education
Enterprise Directory Implementation Roadmap