Subject: Grouper Users - Open Discussion List
- From: Chris Hyzer <>
- To: Gagné Sébastien <>, "" <>
- Subject: [grouper-users] RE: Grouper initial load
- Date: Thu, 1 Mar 2012 15:09:51 +0000
- Accept-language: en-US
The grouper loader does not require existing groups. You need one group to hold the attributes for the job, but that one job can create many other groups based on the ldap filter. Can you explain in detail what data is in ldap, examples of formats, and what you want to the groups to look like after the import and I can give you more info?
From:  on behalf of Gagné Sébastien 
Sent: Thursday, March 01, 2012 9:16 AM
Subject: [grouper-users] Grouper initial load
We were wondering what would be the best way to handle the initial group load in Grouper in an environment where the source (LDAP) has already its set of groups. Is there a tool to do an import ? How did you do it in your org ?
Initially I thought that the Grouper Loader was going to do this, but I realized it was only loading group memberships in existing groups.
Our problem is that we have a large amount of groups and stem/ou in our LDAP, doing it by hand, would not be practical. Our other option would be to create a custom tool that would read our AD and create the stems and groups in Grouper using the API binaries.
Sébastien Gagné, | Analyste en informatique
514-343-6111 x33844 | Université de Montréal,
| Pavillon Roger-Gaudry, local X-100-11
- [grouper-users] Grouper initial load, Gagné Sébastien, 03/01/2012
- [grouper-users] RE: Grouper initial load, Chris Hyzer, 03/01/2012
- Re: [grouper-users] Grouper initial load, Tom Zeller, 03/01/2012
Archive powered by MHonArc 2.6.16.