*Attendees*
Lynn McRae, Stanford U. (chair)
Dave Donnelly, Stanford U.
Gary Brown, Bristol U.
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)
Carry Over *Action Items*
[AI] {Lynn} will write up a generic discussion with use cases of hooks.
[AI] {Tom} volunteered a role in vetting the nearing Signet v1.2 release with Grouper v1.1 to have a common JVM.
[AI] {Kathryn} will send code and links to {Dave} regarding HSQL join queries, and they will speak offline with {Blair} about Hibernate performance.
[AI] Dave will post documentation in I2MI-Commons (CVS), which outlines all the dependent jar files, for use by anyone checking files in or out. (19-Jan-07)
[AI] {Lynn} volunteered to relocate items to the I2MI-Common (CVS), such as loading tools, etc. (9-Sep-06)
[AI] {Tom} will email the list with potential contacts at Macquarie University. (18-Aug-06)
Future *Agenda Topics*
- Kathryn Huxtable - Recent Subject adapter/source activity
*Agenda*
1. Version v1.2.0 - out and available by the call
2. As mentioned in the last call, a subgroup of Signet/Grouper had a call on the concept of "program hooks", an approach to provide sites an easy way to extend Signet and Grouper functionality at key control points without core code modifications or adaptations. We'll review this discussion with a specific focus on defining requirements for Signet and determining the essential control points. There will be a more specific strawman proposal for the call.
*Discussion*
-Signet Release v1.2.0-
{Lynn} announced today as the release of Signet v1.2.0. People may visit the Signet wiki to download the software and view the updated documentation: < https://wiki.internet2.edu/confluence/display/SignetWG/Home/ >.
{Lynn} is will work on final touches for the Signet-demo, available here: < http://signet-demo.stanford.edu/ > (username = kmart, password = signet). {Dave} is working on an interim tutorial for users, which will allow the user to create a Signet data set that corresponds to this wiki document: < https://wiki.internet2.edu/confluence/display/SignetWG/Signet+QuickStart+and+Demo/ >.
-Hooks-
{Lynn} discussed the appeal of both synchronous and asynchronous hooks. He mentioned a use case where a single plugin would act to wrap several hooks together for multiple callins or customizations. Other use cases will come about as requirements are defined. {Lynn} suggested defining adapter classes in Signet as a way to bring consistency to plugins/adapters and the way they are declared in the code. That thought tied into {Dave’s} larger view of the hooks framework, which would be run with the intent to extend basic functionality.
{Lynn} suggested the method we design for declaring these program extensions should be consistent with and can bring consistency to the way all plugins/adapters (e.g., Subject/sources) are declared in the code. That thought tied into {Dave's} larger view of the hooks framework, which would be run with the intent to extend basic functionality.
Example ideas for hooks include precommit, proxy assignments, policy checks. The proposed initial set of hooks for Signet are: pre-commit for both regular and proxy assignments (to apply local business/policy rules), post-commit as well as activation/deactivation events for both regular and proxy assignments (to support real-time enabling), and any assignment evaluation for conditions/rules (for local rules extensions). One plugin would handle the three cases for new, update, and delete. It would ignore those cases not specified, e.g., if it is not interested in a ‘delete’, then it takes no action. Decisions would be made by the plugin, for the plugin – releasing Signet from that responsibility. {Lynn} noted the difference between a privilege change and an assignment, and how that ought to be effected. {Dave} also commented that the rules engine could operate as a plugin, where other reconciliation plugins could exist as rules become more complex.
For additional details, see Lynn’s email to the signet-dev list on 25-May: < https://mail.internet2.edu/wws/arc/signet-dev/2007-05/msg00012.html/ >. {Jessica} will invite interested folks to a follow-up hooks call once a date has been set.
There were no new action items stemming from the discussion.
The next Signet Working Group call will be on Friday, June 8, 2007 at 11am EDT.