Grouper Users - Open Discussion List

[SIAD <>]

Hmmmmm, i don't think so. I would extract a specific attribute value 
from the first request and reuse it for building the second filter.
Actually, i have a first loader job (LDAP_GROUPS_FROM_ATTRIBUTES) who 
initialize empty groups, based on several attributes LDAP (if it's a 
public/private school, an elementary school, an high school...) and the 
school LDAP branche.  There is an ID number for each school and i use it 
as the group name. This ID is the only thing that we have to identify, 
in the employee branche,  the school where employee works.
So, on each empty group (created with the first loader job), i have a 
second loader job (LDAP_SIMPLE) for querying the employee LDAP branche 
with an ldap filter base on each group's name.
It works but it's not really clean. That's why i try to find another 
solution...

I don't know if it's clear for you :-\

Anyway, thanks for your help !

Yoann.

Le 07/10/2013 17:12, Chris Hyzer a écrit :
> Is this something you can do with two loader jobs and intersect the results 
> to an overall group?
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
>
>  
> [mailto:]
>  On Behalf Of SIAD
> Sent: Monday, October 07, 2013 8:53 AM
> To: 
>
> Subject: [grouper-users] Grouper loader LDAP with 2 ldap filters
>
> Hi,
>
> I have a request, is it possible to improve the Grouper loader LDAP with
> the possibility to use 2 ldap filters ?
> Explication : in our LDAP, we have multiple branches. Especially one
> with all schools and second with the employees.
> i would query the school branche and extract a specific attribute value
> in the results entries. Then, use this extract attribute in a second
> filter to query the employee branche and finally create groups with the
> result.
> Pretty much the same behaviour than include_ldap_2level_query option in
> SYMPA :
> http://www.sympa.org/manual/parameters-data-sources#include_ldap_2level_query
>
> Do you think this is possible ?
>
> Thanks,
> Yoann.