120 likes | 237 Views
Strategies for Directory Deployment - Centralized, Distributed, Federated, Decentralized. Presenters (East to West):
E N D
Strategies for Directory Deployment - Centralized, Distributed, Federated, Decentralized • Presenters (East to West): • Suresh Balakrishnan, University System of Maryland Dennis Cromwell, Indiana University - BloomingtonMelinda Jones, University of Colorado at BoulderMark Crase, California State University David Bantz, University of Alaska
Centralized core data Campus applications Contacts: self-service UA Enterprise Directory 2003.10.14 David.Bantz@Alaska.edu
UA Directory Status • 67,000 students; 10,000 employees; 760 departments • Departments fork linked to employees • Web gateway interface supports searching, listing, self-service data • Scheduled & ad hoc batch updates from multiple sources
UA Enterprise Directory StrategyEnvironmental Challenges • Distributed implementation team • Complex interface constraints - based on attributes or roles • Sub-set vs. super-set philosophies
UA Enterprise Directory Responses to Challenges • Two phase commit for self-service edits (Registry/EDir) • Registry (Oracle db) enforces UA rules (syntax, constraints, validation values) • Distributed admin facilitated by attribute-based roles (role-based ACIs)
Directory Search (Anon.) B*ntz
Protecting Information • Employee ids, student ids, social security identifiers are not stored in the Directory • Web gateway intermediary communicates only via SSL • Data changed only by “known” processes (web gateway or MAU IT) • Gateway limits bulk harvesting