Grouper Developers Forum

[David Langenberg <>]

Hi Carl,

We're still working out those details.  The present ideas all center around a standard body semantic for the wire protocol based on JSON with Java interfaces on either end to handle the idiosyncrasies of various messaging platforms.  We hadn't considered either AQMP or STOMP, but since we're looking at message formats now, those are certainly things we can consider.  Do you have any preference or see the overall message community coalescing around one of those?

Dave

On Tue, Jan 27, 2015 at 8:02 AM, Waldbieser, Carl <> wrote:

On the "Post PSP Provisioning" page [1] it looks like the current thinking is that Grouper will be able to target messaging middleware that can then forward the events on to software that does the actual provisioning.  In the last minutes email that went out I noticed this:

  "Grouper will ship with provisioning connectors to internal, AWS and ActiveMQ".

For the ActiveMQ item-- is Grouper going to be targetting a protocol like AMQP[2] or STOMP[3]?  I realize it may be too early for a definitive answer, but I am curious as to whether support for ActiveMQ is going to translate into support for any messaging system that supports a given protocol (e.g. similar to how LDAP and HTTP servers are fairly interchangable) or if there are idiosyncrasies particular to each messaging platform that need to be addressed by Grouper (closer to how the RDBMS landscape looks today).

Thanks,
Carl Waldbieser
ITS System Programmer
Lafayette College


[1] https://spaces.internet2.edu/display/Grouper/Grouper+Messaging+System
[2] http://www.amqp.org/
[3] http://stomp.github.io/

--

David Langenberg

Identity & Access Management

The University of Chicago