Grouper Users - Open Discussion List

[Holger Dippel <>]

Hi Tom,

I've also changed

    <!-- Return members from the "umassd_test_ad" source only. -->
    <grouper:Filter
      xsi:type="grouper:MemberSource"
      sourceId="umassd_test_ad" />

or for the documentation maybe add:

    <!-- Return members from the "ad" source only. -->
    <grouper:Filter
      xsi:type="grouper:MemberSource"
      sourceId="ad" />

This solved the problem with bulkSync.


Holger

Holger Dippel
Director of IT Development and Integration
University of Massachusetts Dartmouth
285 Old Westport Road • North Dartmouth, MA 02747

508-999-9181 •

http://www.umassd.edu/

---

CITS will never ask you for your password or other confidential information via email. Beware of phishing scams where email and/or malicious web sites try to trick users into entering their username and password.
For more information about password security please visit: http://www.umassd.edu/cits/security/

---

From: "Tom Zeller" <>
To: "Holger Dippel" <>
Cc: "grouper-users" <>
Sent: Monday, July 9, 2012 4:13:14 PM
Subject: Re: [grouper-users] PSP with Active Directory

Oh, you were on that page.

I'll read the XML again later, heading out to build-your-house-from-stones workshop for a minute.

On Jul 9, 2012, at 2:10 PM, Tom Zeller <> wrote:

This is documented on that page. I suggest renaming your source to "ldap" in sources.xml.

On Jul 9, 2012, at 10:54 AM, Holger Dippel <> wrote:

I am trying to get a grip on PSP and its internal dependencies. We are using AD and for testing I defined a umassd_test_ad subject source in sources.xml (when setting up Grouper 2.1.1 from source).

The documentation:
https://spaces.internet2.edu/display/Grouper/Grouper+Provisioning#GrouperProvisioning-ConfigureLDAPSubjectSourceIDOtherThan%22ldap%22
states for psp-resolver.xml -- modified for my needs:

<resolver:DataConnector

    id="MemberDataConnector"

    xsi:type="grouper:MemberDataConnector">

    <!-- Return the "dn" attribute of members whose subject source id is "umassd_test_ad". -->

    <grouper:Attribute

      id="dn"

      source="umassd_test_ad" />

  </resolver:DataConnector>

However, the configuration directive in the actual AD sample file reads:

  <resolver:DataConnector
    id="MemberDataConnector"
    xsi:type="grouper:MemberDataConnector">
    <!-- Return members from the "ldap" source only.
    <grouper:Filter
      xsi:type="grouper:MemberSource"
      sourceId="ldap" />-->
    <!-- Return the "dn" attribute of members whose subject source id is "umassd_test_ad". -->
    <grouper:Attribute
      id="dn"
      source="umassd_test_ad" />
  </resolver:DataConnector>

Unless I comment the "grouper:Filter" section out, it would always abort with an error of source "ldap" not being available.


Holger

Holger Dippel
Director of IT Development and Integration
University of Massachusetts Dartmouth
285 Old Westport Road • North Dartmouth, MA 02747

508-999-9181 •

http://www.umassd.edu/

---

CITS will never ask you for your password or other confidential information via email. Beware of phishing scams where email and/or malicious web sites try to trick users into entering their username and password.
For more information about password security please visit: http://www.umassd.edu/cits/security/