Grouper Users - Open Discussion List

[Chris Hyzer <>]

Yeah, set this in the grouper-loader.properties:

 

# by default the top folder for an ldap group of groups is the folder where the config group lives.

# set to false if you want to be able to provision groups to anywhere

loader.ldap.requireTopStemAsStemFromConfigGroup = true

 

 

Note, it is a global setting, so if you have existing jobs, you will have to change those configs so they are absolute in the right spot…

 

Also, there were some Jira’s about this which I believe are all resolved in 2.1.4

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Rob Gorrell
Sent: Tuesday, August 20, 2013 2:15 PM
To:
Subject: [grouper-users] grouper loader - group lists and target stems

 

So i've been playing with the LDAP_GROUP_LIST and SQL_GROUP_LIST loader types and noticed a difference related to the ability to target where (what stem) we load the new groups. In the sql group list, I'm able to have my loader object located in one stem (say loader:orgGroup) and load groups into another adjecent stem (say orgs:) where the loader object isn't located and this works. However, if I try to do the same with the ldap group list by defining a 'LDAP group name _expression_" metadata element (say also orgs:${groupAttributes['cn']}), this path becomes appended to the path of the loader object and creates the groups in :loader:orgs instead of :orgs like the sql group list does.

 

Is there a way to make the ldap group list create an object relative to the root stem instead of its parent loader object?

 

-Rob

--

Robert W. Gorrell
Middleware Engineer, Identity and Access Management

University of NC at Greensboro
336-334-5954