You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Provisioning and Integration (P&I) challenges are urgent across HE & R communities
- P&I projects are everywhere
- New OS registry deployments (CPR and OR) at multiple institutions are anchor tenants for IAM infra and must be wired in
- Grouper deployment projects abound, driving new models of managing service eligibility
- Numerous campuses are on verge of deploying major commercial offerings in this space (OIM, etc.)
- COmanage, CoCoA and SurfConext packages are targeting Research VOs (complementing institutional focus elsewhere)
- HE & R community can take full advantage of the range of current activity IFF we* Articulate a common functional framework within which we can discuss P&I use cases and requirements
- Capture use-case driven requirements across an identified set of projects
- Document solutions emerging from these projects
- Highlight successful aspects of specific projects to guide next round of institutional or VO projects
- We have adequate resources to start this work (additional resources would accelerate progress)
- Change-driven messaging from identity registries (CPR and OR)
- ActiveMQ in CPR
- Amazon SQS, SNS as alternatives to ActiveMQ for queuing and notifications (UDub)
- Camel routes in OR (CAMEL: runnable/configurable Enterprise Integration Patterns)
- Feeding the Identity Registries from the Systems of Record
- Unicon-developed Spring Batch approach
- CPR message-driven approach to SOR integration
- CIFER SOR-to-Registry APIs
- Provisioning engines
- OpenIdM (ForgeRock) investigations at CPR & Stanford
- Extension points:
- CAMEL "routes"
- Activiti for workflows involving humans
- Investigation/Experimentation stage:* ESB: Mule