Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Grouper 1.4.1 LDAPPC

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Grouper 1.4.1 LDAPPC


Chronological Thread 
  • From: Tom Zeller <>
  • To: Ken LAI <>
  • Cc: Grouper Users <>
  • Subject: Re: [grouper-users] Grouper 1.4.1 LDAPPC
  • Date: Tue, 3 Feb 2009 09:31:23 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=bnaWP0DD7sA7OCXUrkB6cb4XQJNZxkv3yS560/fHHA6pHu02vioBFVZVQtrNW3k31K O3wgRBA97faPXp3VleB0gJ0YhblctgioSN0vhzEvX2C6zPTZoWBZO2bhKGJZxwfRalup F5h+GsaMI+c+bqwZZgYgYsMpzIAuRkQeCccUw=

No, unfortunately, it is currently not possible to exclude groups that match any of the <group-queries>.

I would think this issue has been brought up before. Perhaps, in the future, <group-queries> could support union and intersection XML semantics, or <if> <then> statements, or even SQL queries.

In the short term, though, maybe you'll need another custom attribute.

TomZ

2009/2/3 Ken LAI <>
Just tried <attribute-matching-queries> without <subordinate-stem-queries> and it worked.  But how if I want an intersection?   Is it not possible to do it?

Cheers,
-Ken


On Tue, Feb 3, 2009 at 9:30 PM, Tom Zeller <> wrote:
When selecting groups to be provisioned, the results of <subordinate-stem-queries> and <attribute-matching-queries> are combined (aggregated, a union). Did you try <attribute-matching-queries> without <subordinate-stem-queries> ?

TomZ

2009/2/2 Ken LAI <>

Hi,

I tried the new LDAPPC of Grouper 1.4.1 and it worked fine.  However,
I can't select groups to be provisioned by custom group type
attribute.  I have added below custom group type to the Grouper
registry:

<registry>
 <metadata>
   <groupTypesMetaData>
     <groupTypeDef name="mailingList">
       <field name="alias" required="false" type="attribute"
readPriv="read" writePriv="update" />
       <field name="allowAttachments" required="false"
type="attribute" readPriv="read" writePriv="update" />
       <field name="approvers" required="false" type="list"
readPriv="read" writePriv="update" />
       <field name="mailers" required="false" type="list"
readPriv="read" writePriv="update" />
       <field name="moderated" required="false" type="attribute"
readPriv="read" writePriv="update" />
     </groupTypeDef>
   </groupTypesMetaData>
 </metadata>
</registry>

I would like to provision groups with attributed "moderated" only and
so I set in ldappc.xml:

   <group-queries>
     <subordinate-stem-queries>
       <stem-list>
         <stem>hkust:applications:mailinglists</stem>
       </stem-list>
     </subordinate-stem-queries>
     <attribute-matching-queries>
       <attribute-list>
         <attribute name="moderated" value="true" />
       </attribute-list>
     </attribute-matching-queries>
   </group-queries>

All groups under hkust:applications:mailinglists are provisioned
regardless of the value of attribute "moderated".  I tried below and
also didn't worked.

     <attribute-matching-queries>
       <attribute-list>
         <attribute name="mailingList.moderated" value="true" />
       </attribute-list>
     </attribute-matching-queries>

Is custom group type attribute not working with LDAPPC?

Regards,
-Ken






Archive powered by MHonArc 2.6.16.

Top of Page