Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Provisioning to a different kind of target

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Provisioning to a different kind of target


Chronological Thread 
  • From: Jonathan Tellier <>
  • To: Chris Hyzer <>
  • Cc: Tom Zeller <>, "" <>
  • Subject: Re: [grouper-users] Provisioning to a different kind of target
  • Date: Mon, 11 Jun 2012 11:08:29 -0400

> Can you describe in detail the structure of subjects in the ldap,

Here's the info regarding on of my subjects:

DN: cn=elbe,ou=people,dc=example,dc=com
objectClass: person (structural)
objectClass: top (abstract)
cn: elbe
sn: Benson
description: Elizabeth Benson

> and send the part of the sources.xml for this source (sanitized),

<source
adapterClass="edu.internet2.middleware.subject.provider.LdapSourceAdapter">
<id>ldap</id>
<name>LdapSourceAdapter</name>
<type>person</type>

<init-param>
<param-name>ldapProperties_file</param-name>
<param-value>ldap.properties</param-value>
</init-param>

<init-param>
<param-name>Multiple_Results</param-name>
<param-value>false</param-value>
</init-param>

<init-param>
<param-name>sortAttribute0</param-name>
<param-value>cn</param-value>
</init-param>
<init-param>
<param-name>searchAttribute0</param-name>
<param-value>cn</param-value>
</init-param>

<init-param>
<param-name>SubjectID_AttributeType</param-name>
<param-value>cn</param-value>
</init-param>
<init-param>
<param-name>Name_AttributeType</param-name>
<param-value>cn</param-value>
</init-param>
<init-param>
<param-name>Description_AttributeType</param-name>
<param-value>cn</param-value>
</init-param>

<search>
<searchType>searchSubject</searchType>
<param>
<param-name>filter</param-name>
<param-value>
(&amp;(cn=%TERM%)(objectclass=person))
</param-value>
</param>
<param>
<param-name>scope</param-name>
<param-value>SUBTREE_SCOPE</param-value>
</param>
<param>
<param-name>base</param-name>
<param-value>ou=people,dc=example,dc=com</param-value>
</param>

</search>
<search>
<searchType>searchSubjectByIdentifier</searchType>
<param>
<param-name>filter</param-name>
<param-value>
(&amp;(cn=%TERM%)(objectclass=person))
</param-value>
</param>
<param>
<param-name>scope</param-name>
<param-value>SUBTREE_SCOPE</param-value>
</param>
<param>
<param-name>base</param-name>
<param-value>ou=people,dc=example,dc=com</param-value>
</param>
</search>

<search>
<searchType>search</searchType>
<param>
<param-name>filter</param-name>
<param-value>
(&amp;(cn=%TERM%)(objectclass=person))
</param-value>
</param>
<param>
<param-name>firstlastfilter</param-name>
<param-value>
(&amp;(sn=%TERM%)(objectclass=person)))
</param-value>
</param>
<param>
<param-name>scope</param-name>
<param-value>SUBTREE_SCOPE</param-value>
</param>
<param>
<param-name>base</param-name>
<param-value>ou=people,dc=example,dc=com</param-value>
</param>
</search>
<init-param>
<param-name>subjectVirtualAttribute_0_searchAttribute0</param-name>

<param-value>${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('uid'),
"")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('cn'),
"")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('exampleEduRegId'),
"")}</param-value>
</init-param>
<init-param>
<param-name>sortAttribute0</param-name>
<param-value>cn</param-value>
</init-param>
<init-param>
<param-name>searchAttribute0</param-name>
<param-value>searchAttribute0</param-value>
</init-param>
<internal-attribute>searchAttribute0</internal-attribute>
///Attributes you would like to display when doing a search
<attribute>cn</attribute>

</source>

>and give the logs/output when you go to gsh and run:
>
> grouperSession = GrouperSession.startRootSession();
>
> subject = SubjectFinder.findByIdAndSource("theId",
> "sourceIdFromSources.xml", true);
>
> -or-
>
> subject = SubjectFinder.findByIdentifierAndSource("theId",
> "sourceIdFromSources.xml", true);
>
> -or-
>
> subject = SubjectFinder.findByIdOrIdentifierAndSource ("theId",
> "sourceIdFromSources.xml", true);

gsh 10% subject = SubjectFinder.findByIdAndSource("elbe", "ldap", true);
subject: id='elbe' type='person' source='ldap' name='elbe'
gsh 11% subject = SubjectFinder.findByIdentifierAndSource("elbe", "ldap",
true);
subject: id='elbe' type='person' source='ldap' name='elbe'
gsh 12% subject = SubjectFinder.findByIdOrIdentifierAndSource ("elbe",
"ldap", true);
subject: id='elbe' type='person' source='ldap' name='elbe'

Ok, so the subject is resolvable... Then why can't grouper update its
membership?

Thanks,
--jtellier



Archive powered by MHonArc 2.6.16.

Top of Page