...
- (A, l) Asynch architecture, to complement the more synchronous API-based approach
Messaging model where we only send identifiers of changed objects (probably modest effort)
Demo: Grouper changelog publishes events onto an AMQP message transport. What''s available now or soon (RabbitMQ, ActiveMQ); This can be demonstrated with 3.1.b[EthanK] A provisioning/de-provisioning message consumer (perhaps via midPoint) adds/removes people to an external system based on changes in group membership.
[EthanK] Demo Demo: “Human Resource” system puts HR events on a subscribable message queue; Message subscriber reflecting changes into Person Registry
...
- (A, m) Develop guidelines and recommendation in cooperation with InCommon TAC OIDC WG and REFEDs WG
- (A, ?m) First version of Jim Fox's Client-Service Registry (as an advanced CAMP un-conference session)
...
- (A, s) Refine data model for minimal Registry (AI - Warren)
- Map minimal entity registry to midPoint schema (EthanK, WarrenC)
- (A, s) SCIM - user
- (A, m) Midpoint Install
- JimJ has packaged MidPoint and an integrated OpenLDAP into a container so we can implement Warren and Ben's work on the Thin Registry as a start
- Provisioning is a strength of Midpoint that we want to test out
- Perhaps use a Canvas connector for this.
- Implementation to support requirements for Provisioning in the WG
- (A, m?) COmanage Install - support for 3.a through 3.d; Minimal Registry implemented in COmanage
...
(A, m) Building a training course for Grouper, leveraging both the Grouper Deployment Guide and Bill Thompson and Chris Hyzer,
(B, ?m) Demonstrations of more advanced features at Tech Ex (adv camp unconference session proposal)
9) Implement Provisioning tools
...
-
(A, s
) Provisioning to Github via its SCIM API
(A, m) Canvas API connector(s) for midPoint and/or COmanage ; See 2.5
- (B) See above 5.3 and 5.4
...