Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] PSP: grouper:GroupExactAttribute filter does not match attribute

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] PSP: grouper:GroupExactAttribute filter does not match attribute

Chronological Thread 
  • From: Dominique Petitpierre <>
  • To: David Langenberg <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] PSP: grouper:GroupExactAttribute filter does not match attribute
  • Date: Fri, 14 Jun 2013 21:05:06 +0200
  • Authentication-results:; dkim=neutral (message not signed) header.i=none
  • Organization: University of Geneva


On 06/04/2013 07:08 PM, David Langenberg wrote:
Changing from a type to a real attribute would be the best
work-around I can think of.

Trying this work-around I get stuck in a similar place (with Grouper 2.1.3):

The "real" attribute "etc:attribute:ldapSync:syncType" exists for some
groups and can be extracted by an AttributeDefinition like the
following which will put the value in the description of the group
(cf. psp calc output at the end of this message).

<resolver:Dependency ref="GroupWithoutMermbershipsDataConnector" />
<resolver:Dependency ref="UpdateGroupDescriptionChangeLogDataConnector" />

But if the same attribute is used in a grouper:GroupExactAttribute
filter like the following, it does not work and no group is selected:

<grouper:Filter xsi:type="grouper:MINUS">
<grouper:Filter xsi:type="grouper:AND">
value="to_group" />
scope="SUB" />
scope="SUB" />
<grouper:Attribute id="etc:attribute:ldapSync:syncType" />

For example, the following command -psp -calc application:bpm-poc:bpm-oracle:workflow1:bpmpoc -out psp.out

produces the following output in psp.out:

<psp:calcResponse xmlns:psp='' status='failure' requestID='2013/06/14-20:30:49.336' error='noSuchIdentifier'>
<errorMessage>Unable to calculate provisioned object.</errorMessage>
<psp:id ID='application:bpm-poc:bpm-oracle:workflow1:bpmpoc'/>

- What am I doing wrong?
- How should the filter arguments be specified to enable a match?

Otherwise the psp-resolver.xml and psp.xml are OK:

It works if one changes in the above code "grouper:AND" to
"grouper:OR" and the same command produces the following output:

<psp:calcResponse xmlns:psp='' status='success' requestID='2013/06/14-20:32:39.259'>
<psp:id ID='application:bpm-poc:bpm-oracle:workflow1:bpmpoc'/>
<psp:pso entityName='group'>
<psoID ID='cn=bpmpoc,ou=workflow1,ou=bpm-oracle,ou=bpm-poc,ou=application,ou=Groups,dc=unige,dc=ch' targetID='ldap'/>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core' name='objectClass'>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core' name='cn'>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core' name='description'>

It works also, with the same result, if the filter is changed to use
the field "extension" instead of a "real" attribute: e.g.

value="bpmpoc" />

- May be a kind soul could provide me with a working example of psp-resolver.xml
(and psp.xml) that filters groups on the base of "real" attributes?

Thanks in advance for your help!

Mr Dominique Petitpierre, user=Dominique.Petitpierre
IT Division, University of Geneva, Switzerland

Archive powered by MHonArc 2.6.16.

Top of Page