You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

 

Registry

Est

Identity Data and Application Integration (including Provisioning)

Est

Access Mgmt

Est

Authentication Mgmt

Est

Shared Services

Est

< 3 months

ID Match:
- Review/approve high-level requirements
- Identify PM & developer
- Write/approve implementation specs

Registry:
- Review PSU, OR, KIM
- Make recommendation

Med

- Convene interested parties
- Refine workstream task list
- Select use cases for demonstrator implementations

Low

- ID new use cases
- Document new use cases
- First iteration of API standards

Med

- Convene interested parties

Low

- Convene standards/API team

Low

< 6 months

Registry
- Decide on what to build
- Identify PM/developer
- Decide on investment needs
- Solicit investment
- Implementation specs

ID Match:
- Write code
- Begin testing

High

- Toolkit for System of Record (SOR) -to- Registry integration
- 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

Med

- Review workflow tools
- Initial implementation of standards with/in Grouper/KIM

Med

- Confirm analysis/gaps

Low

- Convene cross stream project steering team
- Publish initial standards
- Publish baseline policy & lifecycle use cases

Low

< 12 months

ID Match:
- Testing complete
- Packaging & dates
- Deploy

Registry:
- Development
- Testing plan
- Define interfaces

High

- Toolkit for Registry -to- Identity Consumer System integration (ICS)
- 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 

High

- Complete POCs
- Decide on investment needs
- Use of APIs with/in community (uPortal, Kuali apps, mobile, etc)

Med

- Assess password management requirements & existing code
- Assess OAuth requirements

Med

- Establish UI mgmt console team and environment
- Establish QA/Integration team and environment
- Establish Audit/Report team requirements

High

< 18 months

Registry:
- Testing complete
- Packaging & date
- Early adopter deployment
- Marketing materials

Med

- Reference implementations of identity data and application integration services bundled as installable package(s) 
- Implementation of useful platform integration plugins (Spring, .NET, PHP, etc) 

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
- Create baseline QA/Integration tests
- Create baseline data warehouse and reporting
- Establish training & support team

High

< 24 months

Full deployment

Low

- *Configurable identity & affiliation lifecycle management engine *bundled as an installable package 
- Implementation of useful platform integration plugins (Spring, .NET, PHP, etc) 

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
- Create 2nd version of mgmt console
- Create baseline training & support program

Med

Gimme

- Established code
- SIDS

 

- Existing open source integration stacks: Kuali Rice, Apache ServiceMix
- Registry <=> LDAP integration

 

- KIM/Grouper
- BPEL & workflows

 

EDUROAM/Radius CAS, Shibboleth, Kerberos

 

KEW
Developer tools

 
  • No labels