Grouper Users - Open Discussion List

["Eszes, Gabor" <>]

Have a Grouper-Box client for each Box instance. Each Grouper-Box client has 
its own grouper.client.properties. 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 
grouperBox.messaging.queueName).

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) 
grouper-loader.properties.

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 
grouper-loader.properties: 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.

[1] https://spaces.at.internet2.edu/display/Grouper/Grouper+Box+integration

________________________________________
From:  
<> on behalf of Ryan Rumbaugh 
<>
Sent: Monday, August 5, 2019 3:21:19 PM
To: 
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 
grouper.client.properties 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? 
Thanks!

--
Ryan Rumbaugh