Grouper Users - Open Discussion List

[Scott Koranda <>]

On Thu, Aug 15, 2013 at 3:40 PM, Chris Hyzer 
<>
 wrote:
> Do you have include/exclude enabled in the grouper.properties?

Yes.

>
> grouperIncludeExclude.use = false

I have

grouperIncludeExclude.use = true

>
> Does the type get applied to the group.

It appears it does not. I do have

attributeAssign.getAttributeValueDelegate().assignValue(LoaderLdapUtils.grouperLoaderLdapGroupTypesName(),"addIncludeExclude");

included in the job definition but after it runs and I examine a group
with the UI I do not see anything listed under "Types".

If I use the UI to edit the group I see the checkbox
"addIncludeExclude" for the option "Select group types" but it is not
checked.

How can I get the type applied to the group?

>
> I don't think it matters if you make the group name end in 
> _systemOfRecord...

Ok, thanks. I misunderstood that.


>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Scott Koranda
> Sent: Thursday, August 15, 2013 4:36 PM
> To: grouper-users
> Subject: [grouper-users] LDAP loader and addIncludeExclude
>
> Hello,
>
> I am loading groups from an LDAP directory using grouperLoaderLdapType
> = LDAP_GROUPS_FROM_ATTRIBUTES. I would like to leverage the
> addIncludeExclude functionality and have the composite groups
> automatically created as part of the loader job.
>
> I added
>
> attributeAssign.getAttributeValueDelegate().assignValue(LoaderLdapUtils.grouperLoaderLdapGroupTypesName(),
> "addIncludeExclude");
>
> to the job. I also read this comment in the wiki:
>
> "The reason this enhancement exists is so we can do a group list
> filter and attach addIncludeExclude to the groups.  Note, if you do
> this (or use some requireGroups), the group name in the loader query
> should end in the system of record suffix, which by default is
> _systemOfRecord"
>
> I take that to mean that the name of the group must end in
> "_systemOfRecord" (or something else I can configure) in order to
> trigger the addIncludeExclude and have the composite groups set up. Is
> that correct?
>
> If so, since the "names" of the groups do not end in _systemOfRecord,
> I thought I would add
>
> attributeAssign.getAttributeValueDelegate().assignValue(LoaderLdapUtils.grouperLoaderLdapGroupNameExpressionName(),
> "groups:${groupAttribute}_systemOfRecord");
>
> When I did that the loaded groups in Grouper did indeed end in
> _systemOfRecord, but they were not part of any other created composite
> groups and they had no memberships.
>
> How can I take data out of the LDAP using LDAP_GROUPS_FROM_ATTRIBUTES
> and wind up with the composite groups?
>
> Thanks,
>
> Scott