Items labeled (A) must be delivered by TechEx 2017 Items labeled (B) are intended to be done by TechEx 2017, but the schedule may slip on some of them |
Demo: Grouper changelog publishes events onto an AMQP message transport. A provisioning/de-provisioning message consumer (perhaps via midPoint) adds/removes people to an external system based on changes in group membership.
Demo: “Human Resource” system puts HR events on a subscribable message queue; Message subscriber reflecting changes into Person Registry
(B) TIER HAS to do the API for identity data a la ODS. Longer run we’ll need an implementation package for those APIs.
when APIs are largely defined, consider polling/surveying community for viability with existing systems as input to determining whether or not TIER needs to go build something.
(B) Demonstrate Person data APIs (using the registry, ODS, group repository to populate the user SCIM schema.
(A) Building a training course for Grouper, leveraging both the Grouper Deployment Guide and Bill Thompson and Chris Hyzer pre-conference Grouper training session at Apereo.
(B) Demonstrations of more advanced features at Tech Ex
(B) BennO - Consideration for COmanage Deployment Guide
Not sure that the GDG approach is possible
More likely to take form of screen shares and web cases
(B) Would like to offer either Grouper or COmanage as general tools for SP integration
Enrich SAML-delivered attributes with COmanage identity information to make sure SP gets everything it needs.
Related to provisioning, see 4.3, 4.4, JITime and JICase provisioning; IdP Proxy