Grouper Developers Forum

[Tom Barton <>]

Grouper design call, agenda and bridge info below:

Wednesday, 30 May 2007, 1200EDT (1600Z), 60 minutes

     +1-866-411-0013 (toll free US/Canada Only), or
     +1-800-392-6130 (alternate toll free US/Canada Only)
     +1-734-615-7474 (Non-US/CA, non-toll free, no dialout)
        http://edial.internet2.edu/call/0109331 for SIP
      PIN: 0109331 (followed by "#")

Agenda:

1. administrivia
  . <http://members.internet2.edu/intellectualproperty.html>
  . agenda bash
  . approve minutes
  . review AIs
  . next meeting

2. v1.2.0 - release before v1.1 DB compatibility is ready?
  . outstanding issues
  . documentation
  . release and release candidate target dates
  . release logistics

3. Review of "hooks" conference call; likely Grouper hooks (cf. Lynn 
McRae's signet-dev posting pasted in below).

4. Integration with newly released Signet v1.2.0

5. et cetera

Tom

--

From Lynn McRae's email to the signet-dev list:

Signet program hooks, some high level assertions ...

   * Defined at specific points of program control to address common 
site-specific needs

   * This could provide provisioning hooks among other points of control

   * An easy to configure plugin (or similar) approach that keeps site 
code distinct from Signet (or Grouper) code

   * Not meant to obviate any need to customize the core code itself, 
but should provide high value coverage and ease of product extension.

   * need synch and async capabilities
     (do sync first -- it meets functional needs of both cases)

   * Each point of control should not be limited to a single "listener" 
but be capable of engaging multiple callouts in a site-specified order

   * Might provide a simpler more consistent template for adapter class 
handling in general

   * Keep initial implementation simple!  it can grow.


Proposed Signet hooks:

1) Assignment, pre-commit

- For regular assignments and proxy assignments?
     - Known need for former (regular assignments)
- Requirement is to be able to
     - examine the assignment and approve/disapprove
     - ability to cancel the commit, with a reason code/message
     - possibly augment the assignment information?
- A synchronous invocation of a site specific module
- Uncommitted assignment object is passed as a parm
     - plugin needs to know Assignment API
     - plugin needs to know Subject API for grantor/grantee information

2) Assignment, post-commit

- For regular assignments and proxy assignments?
- Can be asynchronous
- Use case is to take a provisioning action,e.g., invoke message or a 
write to the directory
- Pass the assignment on the call?
- compare assignment vs privilege changes

3) Assignment activation

- For regular assignments and proxy assignments?
- Can be asynchronous
- Not quite the same as post-commit, e.g., for future effective date, 
future prereq activation.  Also a provisioning use case. (Do we need both?)

3) Assignment deactivation

- For regular assignments and proxy assignments?
- Can be asynchronous

5) Assignment reconciliation

- This is when Signet re-evaluates an assignment to see if it has met 
prerequisites or no longer meets conditions.
- Rules handle most of the need here
- a rules interpreter could be implemented as just a builtin hook plugin
- call out should basically implement the same interface as rules, 
returning a boolean true/false evaluation