Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Change log and attribute assign value changes

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Change log and attribute assign value changes

Chronological Thread 
  • From: Peter DiCamillo <>
  • To: Chris Hyzer <>, "" <>
  • Subject: Re: [grouper-users] Change log and attribute assign value changes
  • Date: Fri, 30 Oct 2015 18:31:54 -0400

Thanks, it's GRP-1218, and it includes that additional information.


On 10/30/15 5:52 PM, Chris Hyzer wrote:
Can you please open a jira for this and include how urgent it is to
implement. Also please confirm that you are referring to attribute values
changed in the UI or by other means (WS? GSH?)


-----Original Message-----

On Behalf Of Peter DiCamillo
Sent: Friday, October 30, 2015 5:29 PM

Subject: [grouper-users] Change log and attribute assign value changes

We're using a provisioning model with Grouper where a custom change log
consumer sends messages to endpoints for (nearly) real-time
provisioning. For example, we have an endpoint for Google that will
update Google group membership in response to messages for a
corresponding Grouper group. At this point we're starting to work on
going beyond provisioning membership. We're using group attributes to
provision other information about a target group. For example, we have a
group attribute googleGroupName that specifies the name for the
corresponding Google group. When one of those attributes is added,
deleted, or changed, we'd like to send a corresponding message to the
endpoint. There are change log events for addAttributeAssignValue and
deleteAttributeAssignValue. But when an attribute value is changed, I'd
like to send the endpoints an update message with the old and new
values. I don't seen any change log event for that purpose, and when I
make a change, I get a delete event followed by a separate add event.
Could Grouper be enhanced to include the option of generating a single
update event, instead of separate add and delete events? That would
allow us to use a straightforward implementation, instead of trying to
determine when add and delete events actually represent an update.


Archive powered by MHonArc 2.6.16.

Top of Page