Grouper Developers Forum

[Tom Barton <>]

UChicago is about to use a grouper -> Box provisioner to support its 
first use case: assigning co-ownership to folders created for 
departmental use (as opposed to individual use which eventually go away 
after the individual leaves). This is very far from what one might have 
in mind when discussing "syncing groups to Box". We are starting in a 
very limited fashion because of serious limitations of Box's handling of 
groups. Among the most notable:

Users must type in the names of groups to reference them, and all groups 
are in a single namespace. So don't just slap 10s or 100s of thousands 
of groups out there, and be very careful of how they are named!

Box defaults each new group created to one whose membership is visible 
to everyone, and the group itself is visible to everyone. These defaults 
can only be changed by a Box admin, manually, in a GUI, one at a time.

Each new group is created in Box only when one of its members first logs 
into Box, and Box only adds members to its version of a group as those 
members log in. So it's really hard for a Box admin to know when to go 
to that GUI and manually update the group's permissions, unless of 
course the use case is one in which they usually determine when that 
moment occurs, or if there are no serious consequences.

I hope this helps,
Tom

--
Tom Barton
Senior Director for Architecture, Integration, and Security
Chief Information Security Officer
IT Services
University of Chicago
+1 773 834 1700



On 1/7/2016 7:16 AM, Christopher Sutherin wrote:
> Hi,
>       We are in the process of implementing Grouper.  Does anyone know it a 
> provisioner from Grouper to Box has been created?
>
> Thanks,
> Chris
>
>
> Christopher Sutherin , DB/PS Admin, Business Systems
> Division of Information Technology