*Attendees*
Lynn McRae, Stanford U. (chair)
Dave Donnelly, Stanford U.
Kathryn Huxtable, U. Kansas
Tom Barton, U. Chicago
Michael Gettes, Internet2
Nate Klingenstein, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)
Carry Over *Action Items*
[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 HQL join queries, and they will speak offline with {Blair} about Hibernate performance.
[AI] {Dave} will share a link with the Group for the UML tool, JUDE.
[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] {Dave} will schedule a call with {Blair} to talk offline about coordinating standard procedures for checking files into I2MI-Common. (19-Jan-07)
[AI] {Lynn} volunteered to relocate items to the I2MI-Common, such as loading tools, etc. (9-Sep-06)
[AI] {Dave} will update the requirements text to reflect the upgrade to Java 1.5. (18-Aug-06)
[AI] {Tom} will email the list with potential contacts at Macquarie University. (18-Aug-06)
[AI] {Bob} will send .htaccess local syntax to the group via the list. (5-Aug-05)
*Agenda*
1. I2MI template work on Web site presence
2. Dave has readied a body of Signet UML diagrams and related developer documentation to share
3. Nate will join us to discuss his ongoing work with Signet and Shib and federated privilege management.
4. Upcoming Events – Spring 2007 Internet2 Member Meeting
*Discussion*
-I2MI template work on Web site presence-
{SteveO and Jessica} provided an update on ongoing efforts to update the I2MI web presence. A common look and feel will unify products and projects under the Internet2 Middleware Initiative. The Shibboleth site will be the first product site to be implemented, followed by Signet and Grouper. The proposed target date for the Shibboleth site is by the Spring Internet2 Member Meeting (end of April). The sites will undergo many changes, and will be focused on presenting information to satisfy the various audiences that will visit the site for information. Content for web pages will reside in the most appropriate location, in either the product web or wiki.
-Dave has readied a body of Signet UML diagrams and related developer documentation to share-
{Dave} is in the process of readying a number of UML diagrams, javadocs, Database ERD and other technical documentation for Applications Development in advance of the Signet v1.2 release. {Jessica} will be working with him to avail these items in the wiki. Next, he will be working on wrapping the Signet QuickStart as the QuickStart jar files come together.
{Nate} asked how greatly the upcoming release differs from the latest version. {Dave} said it was mainly the internal architecture that has changed in terms of handling and subjects. While the API has changed, it does not represent significant changes. {Dave} mentioned it might be useful to have a document explaining all the differences between v1.0.3 and the nearing v1.2. The UI has had some changes, though most are internal and will not be easily noticed through use. {Michael} cautioned against using general terms such as “significant” changes, etc., as this may mean several things depending on the audience. With the next release, it will be useful to know which of the changes are of note only to the technical implementers, and which will be of note to the down-stream end user.
-Signet and Shib and federated privilege management-
{Nate} shared a recent effort of his to combine Signet and Shibboleth in a federated privilege management, with the context being a hypothetical VO named “Vortex”. For example, one or more people from multiple organizations come together in a single place where the users and groups could be managed. A person may want to request access to additional resources, or an individual might want to grant access to another person within the VO. They would first access the VO using Shibboleth, with a need to create a local representation. Thereafter, they would use a local signet proxy to grant privileges or request access.
{Nate} has worked with the code, as he was concerned about java exceptions being thrown when trying to find a new person from a source. If a look-up fails, there is no direct relationship to a local representation. Instead of throwing an exception when an ID cannot be found, he wants a local representation to be created at that time.
{Nate} plans on looking into the Subject API to see how it will be a part of Vortex. Eventually, the project will look to incorporate Grouper as well. He hopes to have something in hand by the Spring Internet2 Member Meeting.
-Upcoming Events – Spring 2007 Internet2 Member Meeting-
The next face-to-face opportunity for the Signet Working Group will be at the Spring 2007 Internet2 Member Meeting <http://events.internet2.edu/2007/spring-mm/>. In particular, there will be a combined Grouper/Signet BoF on Monday morning, 23-April. Stay current with meeting room location and detailed meeting abstract at the following link.
<http://events.internet2.edu/2007/spring-mm/sessionDetails.cfm?session=3217&event=267>.
The next Signet Working Group call will be on Friday, March 30, 2007 at 11am EST.