1 / 12

Strategies for Directory Deployment - Centralized, Distributed, Federated, Decentralized

This presentation covers various strategies for deploying enterprise directories, with insights from experts at several universities. It explores centralized, distributed, federated, and decentralized models, highlighting the challenges faced and the solutions implemented. Suresh Balakrishnan, Dennis Cromwell, Melinda Jones, Mark Crase, and David Bantz discuss the development of the UA Enterprise Directory, addressing complex interface constraints and security measures. Learn how their approach serves 67,000 students and 10,000 employees, ensuring reliable self-service access and data protection.

shima
Télécharger la présentation

Strategies for Directory Deployment - Centralized, Distributed, Federated, Decentralized

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. Centralized core data Campus applications Contacts: self-service UA Enterprise Directory 2003.10.14 David.Bantz@Alaska.edu

  3. University of Alaska

  4. 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

  5. UA Enterprise Directory StrategyEnvironmental Challenges • Distributed implementation team • Complex interface constraints - based on attributes or roles • Sub-set vs. super-set philosophies

  6. 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)

  7. UA Directory Architecture SQL

  8. Directory Search (Anon.) B*ntz

  9. Directory Search (Auth.)

  10. Detailed Results (Anon.)

  11. Self-service edits (Auth.)

  12. 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

More Related