Grouper Users - Open Discussion List

[Chris Hyzer <>]

Option1: go by group name (system name), and the column is subject_identifier.  This has worse performance than ID, but might be the only thing possible

Option2: join across a database link to the grouper DB, and get the Id.  You will need to experiment with hints (driving site), to make performance good

 

Thanks,

Chris

 

From: Rob Gorrell [mailto:]
Sent: Monday, October 19, 2015 2:13 PM
To: Chris Hyzer
Cc:
Subject: Re: [grouper-users] Loading SQL Group List but where members are grouper groups

 

admittedly, i'm not a DBA, but does this require both databases (Banner and Grouper) to be on the same server? in the same schema?

-Rob

 

On Mon, Oct 19, 2015 at 11:48 AM, Chris Hyzer <> wrote:

Yes, we do this at penn.  The best thing is to join to the grouper_groups table and use the id (or uuid) of the group to be the subject id to be in the loaded group, and the source id would be g:gsa

 

https://spaces.internet2.edu/display/Grouper/Organization+hierarchies+via+the+grouper+loader

 

ok?

 

Thanks,

Chris

 

 

 

 

From: [mailto:] On Behalf Of Rob Gorrell
Sent: Monday, October 19, 2015 11:39 AM
To:
Subject: [grouper-users] Loading SQL Group List but where members are grouper groups

 

We would like to configure grouper loader job(s) to load the 4-tier organizational hierarchy existing in our ERP, Banner Finance... Campus -> Division -> Unit -> Department. We have already made a loader group to load the bottom 4th level, Departments, where people are directly assigned. But now we would like to roll up and load levels 3, 2, 1 and rather than normalize/flatten them out where users are their members, we would like load the existing level 4's grouper groups as members of the level 3's, and level 3's as members of level 2's, and so on and so forth to automatically create a nested group structure.

But I've never made a grouper loader job where the subject source isn't our external ldap database where user objects are. I assume we can make the subject source to point back at grouper's internal database and then could we send the group name as the subject id?

Am I on the right track of thinking in how to approach such a load?

-Rob

--

Robert W. Gorrell
Systems Architect, Identity and Access Management

University of NC at Greensboro
336-334-5954
PGP Key ID B36DB0CA

--

Robert W. Gorrell
Systems Architect, Identity and Access Management

University of NC at Greensboro
336-334-5954
PGP Key ID B36DB0CA