Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] replication to Google, Phase 2 ....

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] replication to Google, Phase 2 ....

Chronological Thread 
  • From: Jim Fox <>
  • To: Scott Koranda <>
  • Cc: Steven Carmody <>, Grouper-Users <>
  • Subject: Re: [grouper-users] replication to Google, Phase 2 ....
  • Date: Fri, 22 Aug 2014 10:26:48 -0700 (PDT)

We keep a year's worth of course groups. Once a course group
is older than that it is deleted from our group service and
consequently deleted from google. And deleted from our AD.


On Fri, 22 Aug 2014, Scott Koranda wrote:

Date: Fri, 22 Aug 2014 09:38:58
From: Scott Koranda
To: Steven Carmody
Cc: Grouper-Users
Subject: Re: [grouper-users] replication to Google, Phase 2 ....


I know August is a crummy time to ask leading questions since many
people are out on vacation/holiday, but if anybody is provisioning
from Grouper to Google and has thought about what to do for "delete" I
would be grateful if you could drop me a note.



We are interested to know how other campuses deal with "delete" for groups,
in particular course groups. In the current deployment when the course group
is removed from the SOR (LDAP in this case), the loader of course removes it
from Grouper. The custom provisioning code at this point does not call
the Directory
API 'delete' call for the group but instead uses the Groups Setting
API 'patch' call
to change the resource setting for 'archiveOnly' to 'true'. The
primary reason for doing
this is to not "lose" associated "buckets" of information that might
have accumulated
when the group was in use.

What approaches to "delete" for course groups are other campuses taking?


Scott K

Archive powered by MHonArc 2.6.16.

Top of Page