Grouper Users - Open Discussion List

["Farmer, Jacob" <>]

Chris,

 

Thanks for the information! The messaging system seems promising.

 

As for messaging more generally, we do a variety of flavors of queuing based on project, so we’re pretty flexible. For our purposes, we’d probably pick whatever Grouper shipped first.

 

I noticed that SCIM support is there, but in beta…how beta is that? Because we could make that work, too.

 

Jacob

 

 

From: Hyzer, Chris [mailto:]
Sent: Monday, May 1, 2017 2:20 PM
To: Farmer, Jacob <>;
Subject: RE: Grouper hooks and a possible alternate approach?

 

There is built in grouper messaging.  You can configure a change log consumer (already exists, no need to write code), to filter on that group name and send a grouper message.  The thing that needs to be notified can change grouper messaging.

 

We could use better docs for this, and I can improve them if you like, but heres the current link

 

https://spaces.internet2.edu/display/Grouper/Grouper+Messaging+System

https://spaces.internet2.edu/display/Grouper/Grouper+messaging+send+receive+example

 

Do you do messaging at Indiana with AWS, activeMQ, rabbitMQ, azure, etc?  We don’t have adapters for those yet, but if we had one (shouldn’t be hard and we actually are starting to work on them now), we could configure the above connector to just send messages to your message queue system instead of the built in grouper one.

 

The Grouper ESB can send messages out as well, though your system would need to implement a certain HTTP spec or you could do XMPP, though the messaging I think would be preferable…

 

https://spaces.internet2.edu/display/Grouper/Grouper+ESB+Connector

 

If you don’t want to do either of these, then yes, writing a change log consumer would be ideal.  I would use a helper class though, e.g. extend ChangeLogConsumerImpl, and you can mark your class(es) to listen for with an attribute, even if you only have one.

 

https://spaces.internet2.edu/pages/viewpage.action?pageId=14517905

 

Thanks

Chris

 

 

From: [] On Behalf Of Farmer, Jacob
Sent: Monday, May 01, 2017 1:51 PM
To:
Subject: [grouper-users] Grouper hooks and a possible alternate approach?

 

Colleagues,

 

We have been presented with a business need and I’m not sure the best way to resolve it. I would appreciate it if you would be willing to help me brainstorm/consider alternate approaches. I will add that we are new to Grouper and so apologies in advance if this is a trivial problem.

 

We have primarily been working with Grouper to manage LDAP groups in our Active Directory. As we start to consider expanded use cases, we have an application that needs to be notified when a calculated group’s membership changes. Reviewing the docs, there seems to be at least two options: writing a custom grouper hook and creating a worker process that monitors the changelog. We also have a third option in this case: write a separate process that triggers on an update to the LDAP group membership.

 

For those of you who are more experienced -- do any of these jump out as the “right answer”? I’m tempted to write a process to watch the change log because it seems architecturally easiest, but I would appreciate learning from this group’s collective experience.

 

Jacob

 

=========================

Jacob Farmer

Identity Management Systems

(812) 856-0186

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature