Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Box Integration

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Box Integration

Chronological Thread 
  • From: "Eszes, Gabor" <>
  • To: Ryan Rumbaugh <>, "" <>
  • Subject: Re: [grouper-users] Box Integration
  • Date: Mon, 5 Aug 2019 21:32:08 +0000
  • Arc-authentication-results: i=1; 1;spf=pass;dmarc=pass action=none;dkim=pass;arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5f9CnMyy/pVmBnWPgCsCr5NL5AKM4/MLB7DDEY7UeQE=; b=X4RjVmlUfvG+7mKFctueUXJU6VFGoxsXFCtnF5MMEw4uPQFmX+v8zKEHf/lmNgleWkufxlAYoYSLbacek9SRXMDHY+1i4C88yX9R/iHJ1LTclRsXYKFwoTYroi19wuRwP84loqrJ2kJ8WymKQBKqzI4F92bioXdl/D/5PAuBPW0Ccsjw9sEyKA1KLbfQuSIqslntioJZCcuLYogMpmMxzF6SQeLoDQt6U18t1JZC1Ij4W9IcbXg5KRaCuo85F38s1iZjGGwQxRFdRmlsM22pvj3Pbz2cW8JR80JbKpU9bF4/j+ttAbF9zLvYdiU37kwy4MQ+8faS+wq0PIP3zA55YQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=ZwjIgHZdEtvprcMbHg67b1rKeW8j5yWAdW6W4N4XGo/uMN0pRMQslg6koGuYhrIHFv1UH6H9uQqANau6Y21Ik6Va0r67j+162KVMDkxmpCgL28Sn4jqsdv+t8KwzRJEHPqPqfODeIhSZ1rdz4cRwDT2W0B4hE+womPoh8XpUGG3Wr8NFvLaF/FdKTECeEI8Sp/Bag04tR+n5HaapTSIqnlefA3MNvIEh1DUBOnt0O+kmisoeSE+pLmfbeCML777o+j/pU27W1133mJpi1pGODaHmyP7KP0TYujW9jgYhAXpEsZKBgmSXYLUqVHq1EJ4pySMNKAUjOCXkfC5Vphs8RA==

Have a Grouper-Box client for each Box instance. Each Grouper-Box client has
its own The easiest way is to host them out of
different directories on some job server.

Each of them will connect to its own Box (through the grouperBox.clientId and
other config keys), but consumes info from the same source (the value of

For this, use the "Architecture #1" on the Grouper Box integration page [1],
so that the queue serves as the interface between Grouper itself and the
process that will talk to Box. This is configured in the (Grouper server's)

You may opt to have each of these Grouper-Box clients to consume from the
same messaging queue, or you can configure different queues for each (e.g. if
the provisioning criteria are different between your Box instances). If you
use different queues, you'll need additional entries in different changelog consumers that declare their
own criteria and publish to their own queue. You then configure each
Grouper-Box client to consume from its corresponding queue.


<> on behalf of Ryan Rumbaugh
Sent: Monday, August 5, 2019 3:21:19 PM
Subject: [grouper-users] Box Integration

Hi all,

A quick question regarding the Box integration with Grouper. Ideally, we
would like to integrate with multiple Box instances (up to 4) from the same
Grouper instance, but the way I’m reading the documentation the settings don’t seem to be dynamic in a way that
would support more than one Box integration. In particular, the
grouperBox.privateKeyFileName, grouperBox.enterpriseId, etc…

Any suggestions how to configure it to support more than one if possible?

Ryan Rumbaugh

Archive powered by MHonArc 2.6.19.

Top of Page