Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-1218

New change log event for attribute assign value updates



    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.2
    • Fix Version/s: None
    • Component/s: API
    • Labels:
    • Environment:
      Any supported environment.


      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 see any change log event for that purpose, and when I
      make a change, I get a delete event followed by a separate add event.
      Please enhance Grouper to include the option of generating a single
      update event, instead of separate add and delete events. The update event should include both the old and new values. That would
      allow us to use a straightforward implementation, instead of trying to
      determine when add and delete events actually represent an update.

      We need this to work regardless of how the attribute values are changed. We use the UI, WS, GSH and the Java API. We'd like it fairly soon, but it's not urgent. A patch to 2.2.2 would be good, waiting for 2.2.3 would probably be too long. For our use of Grouper, there'd be no need to keep the current behavior available as an option.

        Smart Checklist




              • Assignee:
                chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
                peter.dicamillo@at.internet2.edu Peter DiCamillo
              • Votes:
                1 Vote for this issue
                2 Start watching this issue


                • Created: