Registry

Identity Match

• Gimmes - no viable source systems for this, but work has been done to come up with a design for an id match solution
• 6 months - First release (0.9 status) of core identity match functionality which could potential be deployed by brave early adopters (would include api, algorithm implementation, most of flow 1 and flow 2, possibly not "interactive" component)
• 12 months - 1.x release, including "interactive" component (which would likely include integration with a workflow or notification component), Integration with OSIDM4HE registry or registry solutions via standard integration points, documentation
• 18 months - Deployment work underway at > 1 institution, continued outreach, documentation and training efforts, work underway on a reference implementation of a Self Service UI console, at least one early release of console
• 24 months - Full production deployment at multiple institutions

Core Registry

• Gimmes - have multiple possible "source" systems from which to build on or pull "best of breed" practices for the core registry
• 6 months - have done analysis and decided on direction regarding which system or systems upon which to build, project plans and milestones established, resources in place, at least one iteration on standard api design, development of functionality underway focussing on implementation of data model/storage and api design/implementation for the registry, at least one early (0.x) release available upon which early adopters could begin implementation work
• 12 months - 1.0 version available, including the registry requirements identified by the registry group as well as extensibility, events happening in the registry are can be used to provision downstream, built-in integration with deliverables from the provisioning team
• 18 months - Implementation work underway at > 1 institution, continued outreach, documentation and training efforts
• 24 months - Full production deployment at multiple institutions

Access Management

• Gimmes - KIM and Grouper both implemented and in wide use, some work has been done with the FIFER-API efforts and the Access Management group on designing standard apis
• 6 months - At least the first iteration of documented api standards for groups, roles, and permissions along with implementation (either complete or in-progress) in KIM and Grouper
• 12 months - get commitment for usage of apis within projects within our communities (i.e. uPortal/Mobile, other Kuali projects themselves, Sakai...others?) and hopefully some amount of early adoption within our community
• 18 months - Implementation of useful platform integration plugins to some common platforms (spring, .net, php, Ruby/Rails, etc.)

  The group discussed and thought that it would make sense to move this higher on the list into the 12 month time frame since these platform integration points might help to drive adoption on top of these new apis and provide for a "standard" way to take advantage of them inside of various technologies.

• 24 months - Access certification and risk assessment?

  Group suggested renaming this to Access Audit and Monitoring