Grouper Developers Forum

["Jessica Bibbee" <>]

Grouper Working Group Meeting
September 5, 2007

 

*Attendees*
Tom Barton, U. Chicago (chair)

Steve Carmody, Brown U.

James Cramton, Brown U.

Dave Donnelly, Stanford U.

Bill Kasenchar, U. Pennsylvania

Ann West, EDUCAUSE/Internet2

Michael Gettes, Internet2

Jessica Bibbee, Internet2 (scribe)

 

New *Action Items*

[AI] {Tom} will email the list with instructions for downloading the v1.2.1 API frozen in CVS.

[AI] {James} will open a JIRA issue on and work with {Michael} to contribute to LDAPPC development.

[AI] {Jessica} will inquire about creating an I2MI-Common area in JIRA.

[AI] {Dave} will assemble a hooks sketch for Grouper, staking out the mid-level perspective.

[AI] {Michael} will share his write up on discussion of items A2 and B2 for feedback regarding priorities for substantial functional enhancements.

 

Carry-over *Action Items*

[AI] {Shilen} will repeat profiling and other diagnostics to gauge progress on GRP-6.

[AI] {Klara} will ask power-users at Duke for feedback on their searching requirements.

[AI] {Shilen} will contribute to the JNDI and/or JDBC development work.

[AI] {Tom} will share a write-up of his vision of a large-scale item that addresses integration of the I2MI-Common software and where it fits into the roadmap.

 

*Agenda*

1. Readying release 1.2.1.
2. Using AspectJ to implement hooks.
< https://wiki.internet2.edu/confluence/display/GrouperWG/Hooks >
< https://wiki.internet2.edu/confluence/display/GrouperWG/Candidate+Grouper+API+Hook+Points >

3. Priorities for substantial functional enhancements.
< https://wiki.internet2.edu/confluence/x/NBk >

*Discussion*

 

- Readying release 1.2.1-

The final version of the Grouper v1.2.1 API is now available in CVS under the name 'Grouper_1_2_1_FREEZE'. Included are all the changes and fixes that {Blair} plans to include for the official v1.2.1 of Grouper. Next, {Gary} will make final updates to the UI and a release will be available shortly. No target date has been set. [AI] {Tom} will email the list with instructions for downloading the v1.2.1 API frozen in CVS.

 

A few of the v1.2.1 changes will address issues in Ldappc. [AI] {James} will open a JIRA issue on and work with {Michael} to contribute to LDAPPC development.

 

The Group also expressed a desire to expand the projects in JIRA to include I2MI-Common. This area will house those fixes related to common middleware projects, such as Signet and Grouper both. [AI] {Jessica} will inquire about creating an I2MI-Common area in JIRA.

 

- Using AspectJ to implement hooks.-
{Tom} shared an update of a prototype demonstration by {Marcus Dübois and Leif Johansson} for using AspectJ (see also Marcus' email on 9-Aug.) This demo showed that logging is possible using this technology. What more should the Group specifically look to do?  See the below pages in the wiki to view Marcus' work.

< https://wiki.internet2.edu/confluence/display/GrouperWG/Hooks >

The below link offers a collection of items one would want to hook into the Grouper API: < https://wiki.internet2.edu/confluence/display/GrouperWG/Candidate+Grouper+API+Hook+Points > {Tom} asked the Group to consider functional requirements. He envisions a high-level document outlining the items that they will want to address. A few starter items include:

 

1) Logging – replace API with AspectJ as log-writing technology, but enforced in infrastructure

2) Change Notification – LDAPPC would not need to compute, but would be notified of specific changes

3) History and Audit – keep a log of who has done what to what, with the source of the information coming from AspectJ infrastructure

4) Integration – LDAPPC would provision changes, but use other technologies like JMS (Java Messaging Service) or real time messaging; have one or more classes hooked into the infrastructure, so changes in Grouper can be sent to/via your institution messaging infrastructure

5) Business Rules – criteria that factors in business logic, such as "Do not allow Someone to add to this group unless other Conditions hold." It would provide a check to see if you still want that operation to proceed.

The Group did not identify a specific timeframe to address the above items. The next task is to address the functional requirements that will determine the basic infrastructure to which one can hook in experimental classes.

 

{Dave} mentioned that using AspectJ requires previous experience. While it might very well have its place in the Signet/Grouper projects, it may be less useful for implementing business rules. He agreed it would be good for logging and low-level items, but cautioned against using AspectJ for all levels, i.e., it might be too detailed for notification, etc. For this, a higher-level non-methods-based presentation in the API could be used.

 

The Group recognized a need for a mid-level interface capable of addressing these concerns. {Dave} advised that the first task is to gather requirements, define what they plan to do, and only then decide how to implement that. [AI] {Dave} will assemble a hooks sketch for Grouper, staking out the mid-level perspective.

 

- Priorities for substantial functional enhancements-
The Group discussed the 2006 document outlining priorities for substantial functional enhancements < https://wiki.internet2.edu/confluence/x/NBk >, which needs updating. Items A2, A3 have been started but not completed. Items B2, B3, and B4 have yet to be started. Integration topics related to I2MI-Common need to be added to the list.

[AI] {Michael} will share his write up on discussion of items A2 and B2 for feedback regarding priorities for substantial functional enhancements. He also reiterated a need for the Group to not lose sight of the importance of Ldappc, and the fact that it needs a proper owner/home such that the appropriate modifications can be made to increase performance and flexibility.

 

-Update from Brown University-

{James} shared a few concerns around the UI. The next phase is adoption, then they will work to get feedback from users and further address how to 'skin' this for their purposes.  Brown U. has just released Grouper into production, and they are still learning as they proceed – for example, how to point applications to Grouper, and how to educate users on this process.

 

The next Grouper Working Group call will be held on Wednesday, September 19, 2007 at 12pm EDT.

-- 
Jessica Bibbee, Technical Analyst
Internet2

mobile: +1-734-255-6644

Dive into the next wave of innovation:
Register for the Internet2 Member Meeting
http://events.internet2.edu/2007/fall-mm/