Grouper Users - Open Discussion List

[Shilen Patel <>]

We talked about this on the Grouper call.  One option may be to use a virtual directory like OVD (not sure off hand about open source options).  OVD would provide the LDAP interface.  When LDAP calls are made to OVD, it can trigger custom built adapters that can then call Grouper.  So the adapters would serve as the gateway without having to implement the LDAP protocol.  Just a thought.

By the way, if your current need could be accomplished by SQL queries, you could use the views that come with Grouper.

Thanks!

-- Shilen

From: Julio Polo <>
Date: Monday, October 14, 2013 7:18 PM
To: Peter DiCamillo <>
Cc: "" <>
Subject: Re: [grouper-users] Detecting membership changes

I noticed that L-Soft's LISTSERV supports dynamic queries (SQL or LDAP) so I could avoid synchronization altogether if I had an LDAP-to-Grouper gateway.   Such a gateway would be useful beyond LISTSERV as well.  It'd be great if I could issue an LDAP search and have the gateway perform a web service call to Grouper and return the info as LDAP attributes.  It would be much better than replicating all Grouper memberships into LDAP.

-julio

On Mon, Oct 14, 2013 at 9:42 AM, Julio Polo <> wrote:

Thanks Peter.  That's a great idea, except that I would still need to detect group membership changes in order to update the LDAP group.  Our enterprise messaging can provision institution-defined Grouper groups (and LDAP groups), but there are ad hoc user-maintained groups that are factors in composite groups.  I need to detect effective membership changes for composite groups so that the corresponding LISTSERV list (or LDAP group) can be updated.

-julio

On Fri, Oct 11, 2013 at 6:26 PM, Peter DiCamillo <> wrote:

If you're referring to the L-Soft LISTSERV product, have you considered using Listserv's support for dynamic lists based on LDAP? Using that, Grouper would only have to provision LDAP groups for use by Listserv.

Peter

On 10/11/13 11:43 PM, Julio Polo wrote:

Hi Chris,

Has anything changed in the last two years since I posted this question
on detecting membership changes?  I don't need email notifications, and
we are on Grouper 2.1.5.  The change log option sounded like the most
efficient way of doing this, but that only applied to pre-2.0?  What are
my options?  I need to synchronize LISTSERV lists as members are added
or removed from specific groups.

Thanks!

Julio Polo
University of Hawaii



On Fri, Oct 7, 2011 at 10:32 AM, Chris Hyzer <

<mailto:>> wrote:

    We have the last membership changed in the DB, but we don't expose
    over WS, I supposed we could in a later version.

    If you have 2.0, there is a rule for email notifications:

    https://spaces.internet2.edu/display/Grouper/Grouper+rules+use+case+-+Email+notification+on+flattened+membership+remove

    You could need a rule for add, and a rule for remove.  Note you can
    have this work for all groups in a folder with one rule.

    Also, (applies to pre-2.0), you could use the change log to send an
    event somewhere (e.g. xmpp or ws), or send them email directly from
    the change log consumer.  This would be very easy to setup and I
    could send you a code example if you need it.   Just send me the
    exact requirements.

    Generally the architecture of the change log allows us to avoid
    polling via ws (has the membership changed?  Has the membership
    changed?  Has the memberships changed? Etc) which is why it might
    not be ideal to add to the WS api :)

    Thanks,
    Chris

    -----Original Message-----
    From:
    <mailto:>

    [mailto:
    <mailto:>] On Behalf Of Julio Polo
    Sent: Friday, October 07, 2011 4:05 PM

    To: <mailto:>
    Subject: [grouper-users] Detecting membership changes

    Is there a web service for detecting whether members have been added
    or removed from a group?  I'm contemplating an application that sends
    us email whenever someone is added or removed from a group.  Is the
    audit functionality the best way to achieve this?  I didn't see a web
    service for it, though.  Or shall we just do a periodic dump of the
    entire membership and diff for changes?

    Julio Polo
    Identity and Access Management
    University of Hawaii