• Search site
• A-Z
• Directory
• myUVM

• UVM Home
• Computing & Information Technology: LDAP Project
  • Project Definition
  • LDAP Background Information
  • Requirements
  • Evaluation Criteria
  • Comparison Matrix
  • General Object Classes
  • UVM Object Classes
  • Who Can See My Information?
  • CSO to LDAP mapping
  • Schema Files
  • Example Entries
  • Comments
  • Submit Comments

Requirements

Have to Have

1. Be the corporate directory for UVM
2. Have an entry for every person affiliated with UVM
3. Directory lookups (for email clients and direct search)
4. List every affiliation a person has with UVM
5. Private entries that only an administrator (CSO "hero") can access (to support mail aliases for people who do not want their information published)
6. Web interface (a.k.a. UVM White Pages)
7. Aliases that expand to multiple email addresses
8. Provide the "network id" for every person affiliated with UVM
9. Provide authentication services by deferring to DCE security server
10. Provide a method for people to change their DCE password via the LDAP server
11. Kerberos/DCE password strength/validity requirements enforcement
12. Not cost a fortune
13. Allow people to update the same fields in their LDAP entry they can update in their CSO entry today

Nice to Have

1. Support from CS&T for storage of calendar data in this LDAP server

Last modified April 26 2001 03:02 PM