70 likes | 198 Views
Middleware: Directories. Groups related work. Dr. Tom Barton The University of Memphis. Why do groups?. Leverage existing enterprise directory infrastructure to: Supply data for access control policies to directory integrated applications and service platforms.
E N D
Middleware: Directories Groups related work Dr. Tom Barton The University of Memphis
Why do groups? • Leverage existing enterprise directory infrastructure to: • Supply data for access control policies to directory integrated applications and service platforms. • Supply data for customization processes, especially CMSs and portals. • Facilitate group messaging. Middleware: Directories
Practices in Directory Groups:Why read it? • Avoid excessive wheel re-invention & toe stubbing: • lessons learned • examples of good & bad practices • Pick up common terminology and conceptual framework. • Provoke thought. • Potential & alternative solutions Middleware: Directories
Design factors for a groups implementation • How the group information is to be maintained • How it is to be most commonly accessed • How potential interactions arise between the type of representation, the nature of the group (eg, size and privacy requirements), and capabilities of the particular directory service agent being used Middleware: Directories
Selected contents • Delegating management • Referential integrity • Personal groups • Privacy & visibility • Group math • Forward referencing • Aging • Namespace issues • Application examples Middleware: Directories
Whither next? • Groups Implementation Guide (Eileen Shepard, Michael Gettes, tjb, others??) • BoF topic tonight – what do you want to see in it? • Roles, relations, and access control architecture: Is this an extension to “core middleware” that ought to become commonplace? • Standardization of isMemberOf? Middleware: Directories
Links • http://middleware.internet2.edu/dir/groups/ • http://www.nsf-middleware.org • tbarton@memphis.edu Middleware: Directories