Page History

...

1. (A, m) Definitive TIER API Guideline document; The excavation, sifting and winnowing are likely to be the labor intensive bits.
2. (B, s) Evaluate need for Grouper permission and policy management
3. (A, m) SoR/Registry/ODS/Groups (for TechEx needs; Ultimately it will end up being Large)
4. (A, s) Registry to Grouper: Registry is authoritative source of subjects (LDAP, JDBC, API later?)
5. (A, s) Provisioning (for demo purposes, based on UW-Madison Global Summit demo)
6. (A, s) Consent-informed Attribute Release (CAR)
   1. External API authored by Marlena
   2. Presentation to TIER-API prior to their review of the API
7. (B, m) Certificate API
   1. An API for server certificate management for use by InCommon (check with ChrisHubing and JimJ)
   2. JimJ will would help with a Comodo proxy

3) Define and implement an event-driven messaging approach

1. (A, l) Asynch architecture, to complement the more synchronous API-based approach
   1. Messaging model where we only send identifiers of changed objects is probably small

   2. 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.

   3. Demo: “Human Resource” system puts HR events on a subscribable message queue; Message subscriber reflecting changes into Person Registry

...