Subject: Grouper Users - Open Discussion List
- From: Rahul Doshi <>
- To: Chris Hyzer <>, "" <>
- Subject: [grouper-users] Re: Grouper ldap loader
- Date: Thu, 26 Jul 2012 20:28:43 +0000
- Accept-language: en-US
Yes, I am using LDAPGROUPLIST job and group is being returned from the ldap filter. I will try to use the example from the link you provided.
From: Chris Hyzer <>
Date: Thursday, July 26, 2012 4:23 PM
To: Rahul Doshi <>, "" <>
Subject: RE: Grouper ldap loader
Actually, is this an LDAP_GROUP_LIST job, and is cn=someotherstem:admins, ou=group, dc= example, dc = org one of the groups that is returns from the ldap filter (as well as a member of a group). If so, then with the link below, you can do what you want to do. If that member which is a group is not managed by the loader, so we can do this with a tweak to grouper or an EL tweak. Let me know
I hadn’t really considered that case when creating the loader, but I think it can be done fairly easily with some EL and a java class. It is very similar to this email, except that the group will be created perhaps in EL…
Want me to try to send you an example?
I am trying to use grouper loader to load all the existing groups from our ldap environment. It seems to load the groups fine except that it is ignoring the nested group membership. For hypothetical group below if I run the loader job, I only see somstem:admins group created in grouper with member xyz. What I would have expected to see is two groups somestem:admins and someotherstem:admins created in grouper and someotherstem:admins also be the member of some stem:admins. Is there something that I am missing in my configuration?
cn=somestem:admins, ou=group, dc=example, dc=org
member=cn=someotherstem:admins, ou=group, dc= example, dc = org
- [grouper-users] Grouper ldap loader, Rahul Doshi, 07/26/2012
Archive powered by MHonArc 2.6.16.