Grouper at New York University
May 2016
NYU Classes requested the ability to create Google Groups where it’s the authoritative source for memberships of a Sakai course site and keep memberships in sync. Groups in Sakai are marked as “Shared with Google Groups” whose members of those groups kept in sync with a corresponding Google Group. Each change in Sakai needs a corresponding change in Google and that's accomplished by a sync job that watches Sakai and applies changes (via a loader job) to Grouper which then the Google Changelog consumer acts on to provision to Google. Since course sites are in Grouper, it provides an integration point to expose course site membership information to other systems within NYU. For more info, NYU presented at the Open Apereo 2016 conference the presentation Grouper in Action at NYU.
June 2015
See the June 2015 update from NYU on Selective Group Exclusion When Provisioning to LDAP.
October, 2013
NYU has been running Grouper for several years. Our production instance now sports some 125K folders, 204K groups and
500K members -- mostly consisting of groups created to mirror class enrollments.
We have only used Grouper for a few applications to date, but are now embarking on a major project to integrate groups
across Sakai, Grouper and Google Groups, with implementation in the Spring 2014 timeframe.
A major challenge for the future is figuring out how best to manage groups and make group data available across a number
of core identity management tools which have overlapping capabilities vis-a-vis groups: Grouper, Sailpoint IIq (our newly
adopted role/account management system), LDAP, Active Directory.
- Gary Chapman, NYU/ITS - gary.chapman @ nyu.edu