Project Definition
Name
FootPrints/LDAP Integration
Project Description
Roll out version 6 of FootPrints complete with the MySQL interface for the backend database and LDAP integration for authentication and address book
Statement of the Problem to be Solved
The current implementation of FootPrints uses an internal address book and flat files (gdbm) to hold both the address book(s) and project databases.
Because the data is stored in flat files, the access/update time increases as the amount of data stored increases. The address book(s) are each separate from each other as well as being separate from the central identity management system.
This version of FootPrints fixes the performance problems by storing the project databases in MySQL databases and using LDAP for the address book.
Sponsor
Computing and Information Technologies (CIT)
Costs (one-time)
The one-time costs are the purchase of the new version and the purchase of the LDAP authentication license.
Costs (on-going)
Continued maintenance costs for FootPrints per year.
Benefits
This version of FootPrints will allow CIT to handle more problems in a timelier manner because the size of the project database will not have a direct impact on the performance of that database, since MySQL has excellent access times.
Utilizing LDAP for the address book and authentication mechanism will leverage the work put into the central identity management system and LDAP directory to assist with the timely addition/removal of address book entries.
Dependencies
- Availability of FootPrints code the first week of June.
- Availability of a test machine.
- My time.
Last modified May 21 2003 08:30 AM