Grouper Users - Open Discussion List

[Tom Zeller <>]

> We have successfully been testing LDAPPCNG provisioning from Grouper into 
> the Active Directory, and have been working on filtering out the groups 
> that we need provisioned. We have this working at the moment by defining a 
> group filter in the GroupDataConnector, this currently filters on stems,
>
> <resolver:DataConnector id="GroupDataConnector" 
> xsi:type="grouper:GroupDataConnector">
> <grouper:GroupFilter xsi:type="grouper:Minus">
>    <grouper:GroupFilter xsi:type="grouper:StemName" 
> name="Applications:Filestores:ISS" scope="SUB" />
>    <grouper:GroupFilter xsi:type="grouper:StemName" name="CorporateData" 
> scope="SUB"/>
>  </grouper:GroupFilter>
>   <grouper:Attribute id="members" />
>    <grouper:Attribute id="groups" />
>  </resolver:DataConnector>
>
> This successfully provisions the groups that live under 
> "Applications:Filestores:ISS", however it creates the stem structure for 
> CorporateData, i.e. it will create the hierarchical folders for our org 
> structure without the actual departmental groups.
>
> Is there anything that we need to add to the Ldappc-resolver to stop empty 
> folders being created within the AD? Maybe a filter within the 
> StemDataConnector?

Yes, add the same <GroupFilter ... /> element of your
GroupDataConnector to the StemDataConnector. Does that work ?

TomZ