Design Meeting - 2008-11-05
Attendees
1. ~steiner Dave Steiner
2. Nancy Mond
3. ~dima767 Dmitriy Kopylenko
4. ~battags ScottS
Term Definitions
- System of Record - Authoritative source of information. Responsible for providing accurate information.
- Downstream System - Systems that are fed from the OpenRegistry. Rutgers is looking at scoping this to only include systems that things belong to the Identity Infrastructure. Other systems that need data should look to standard APIs such as LDAP.
...
- Messaging Queue for downstream systems to poll for retrieving updates. This may be a system such as LDAP or a deprovisioning tool watching for specific items.
- Audit Log should be specific enough that we can track redo, undo and troubleshoot, whether its automatic or manual.
- Batch, Real-time, and Web Interface. Real-time could be REST, SOAP, JMS, etc. Web Interface is a UI for entering data in real time, using the OpenRegistry as a system of record.
Full Scope
- Provide the following repositories: People, Group, Course, Account, Credential
- Support the following populations: students, continuing ed students, joint program students, alumni, new employees, faculty, staff, retirees and guests.
- Support updates via: batch, real-time (system-to-system), web interface (manual input)
- Perform following input processing:
- normalization
- reconciliation
- generate attribute data based on rules
- populate repositories based on rules
- provide identifier assignment for new individuals
- Provide services:
- accept data from SORs
- expose data to downstream systems feeding identity infrastructure
- Provide permssion model for privacy policy enforcement
- Provide audit capability that may be used for trouble shooting and manual/mechanized error correction.
Release 1 Scope
- Focus on Guest Management
- Is Real-time Interface needed at this point?
- Batch and Web UI appear needed
- Input Processing may be simpler