|
September 2007
The “large” UM campus (UM-Missoula) is now running a “Version 0.9” central directory system
- Synchronizing real directories, namely Oracle Internet Directory (OID) and Microsoft Active Directory (AD), in which the structure and individual entities (identities) have been systematically defined and assigned (but also must co-exist with legacy structure and accounts, particularly in the AD)
- Based on a simple “Version 0.9” schema,
using data systematically fed from our enterprise information
system (Banner)
- Authenticating campus staff and students into numerous Windows and Unix/Linux applications, including public lab access, wireless, email, the Blackboard course management system, the on-line library system, and other unit-based applications
The next steps, along several orthogonal paths:
For policy support (Fall 2007)
- Create an Identity Management Oversight Committee with broad responsibilities covering central directory services but also related policy and business practice
For actual directories (Fall 2007/Spring 2008)
- Clean up legacy issues
- Extend delegation capabilities to unit-based system administration staff (i.e., using Signet, Grouper or comparable tools)
- Extend use of central directory to other campus applications and workgroups
- Extend integration with directory structures concurrently evolving at the other three campuses
For schema development (Spring 2008)
- Roll out new “Version 1.0” consisting of Eduperson attributes along with any local modifications and/or extensions we discover we need
For authentication and authorization (Winter 2007/Spring 2008)
- Introduce central authentication service to handle the authentication and authorization dialog uniformly and consistently across all local apps, as well as to smooth transition of authenticated/authorized users from application to application without additional authentication. This is to be done with Central Authentication Service (CAS) and Shibboleth.
For the overall environment (2008/2009)
- Prepare to participate in the global federation, such as through InCommon
- Prepare to extend systematic authentication/authorization across the four campus UM environment
|
