Matrix below shows major workstreams in columns and the tasks / deliverables over 6 to 24 months in rows. Resources Estimates assume 1 FTE for Low, 3 FTE for Med, and 5 FTE for High. This is the estimated number of development or support resources needed for the specified tasks / deliverables per period. Registry Est Identity Data and Application Integration (including Provisioning) Est Access Mgmt Est Authentication Mgmt Est Shared Services Est < 3 months ID Match: Med - Convene interested parties Low - ID new use cases Med - Convene interested parties Low - Convene standards/API team Low < 6 months Registry High - Toolkit for System of Record (SOR) -to- Registry integration Med - Review workflow tools Med - Confirm analysis/gaps Low - Convene cross stream project steering team Low < 12 months ID Match: High - Toolkit for Registry -to- Identity Consumer System integration (ICS) High - Complete POCs Med - Assess password management requirements & existing code Med - Establish UI mgmt console team and environment High < 18 months Registry: Med - Reference implementations of identity data and application integration services bundled as installable package(s) Med - Implementation of useful platform integration plugins (Spring, .NET, PHP, etc) Med - Deliver beta password management services in registry, portal context Med - Create baseline management console High < 24 months Full deployment Low - Configurable identity & affiliation lifecycle management engine bundled as an installable package High - Access audit & monitoring (Access requirement fulfillment) Low - Assess social to SAML gateways? (Ties to Registry and/or Acct Management; Need identities) Med - Create 2nd version of audit/reports Med Gimme - Established code - Existing open source integration stacks: Kuali Rice, Apache ServiceMix - KIM/Grouper EDUROAM/Radius CAS, Shibboleth, Kerberos KEW
- Review/approve high-level requirements
- Identify PM & developer
- Write/approve implementation specs
Registry:
- Review PSU, OR, KIM
- Make recommendation
- Refine workstream task list
- Select use cases for demonstrator implementations
- Document new use cases
- First iteration of API standards
- Decide on what to build
- Identify PM/developer
- Decide on investment needs
- Solicit investment
- Implementation specs
ID Match:
- Write code
- Begin testing
- Person identity schema mappings to/from RDBMS/SCIM/SAML/LDAP
- Demo/Reference SOR-Reg integration solution (e.g., Oracle HCM or Workday to Registry) built with toolkit
- Initial implementation of standards with/in Grouper/KIM
- Publish initial standards
- Publish baseline policy & lifecycle use cases
- Testing complete
- Packaging & dates
- Deploy
Registry:
- Development
- Testing plan
- Define interfaces
- Demo/Reference Reg-ICS integration solution (e.g., Registry to Account & Credentialing System, SIS & LMS) built with toolkit
- Toolkit of identity data and application integration services
- Decide on investment needs
- Use of APIs with/in community (uPortal, Kuali apps, mobile, etc)
- Assess OAuth requirements
- Establish QA/Integration team and environment
- Establish Audit/Report team requirements
- Testing complete
- Packaging & date
- Early adopter deployment
- Marketing materials
- Implementation of useful platform integration plugins (Spring, .NET, PHP, etc)
- Create baseline QA/Integration tests
- Create baseline data warehouse and reporting
- Establish training & support team
- Implementation of useful platform integration plugins (Spring, .NET, PHP, etc)
- Create 2nd version of mgmt console
- Create baseline training & support program
- SIDS
- Registry <=> LDAP integration
- BPEL & workflows
Developer tools