Page History

...

Heather Flanagan, Internet2 (chair)
Ken Klingenstein, Internet2
Chris Hyzer, U. Penn
Keith Hazelton, U. Wisc
R.L. "Bob" Morgan, U. Washington
Steven Carmody, Brown U.
Jim Leous, Pennsylvania State U.
Benn Oshrin, Internet2
Steve Olshansky, Internet2

New Action Items

Wiki Markup\[AI\] Heather will track on a wiki page approaches to sharing metadata between collab platforms.

Carry Over Action Items

Wiki Markup\[AI\] (Ken) will develop a one-page writeup on the differences between a VO IdMS versus an enterprise IdMS \
[AI\] (Benn and Keith) will talk about Bamboo's requirements for person registry. \
[AI\] (Ken) will email Bob B. regarding the possibility of speaking at ACAMP \
[AI\] (Heather) will schedule an Internet Identity webinar for iPlant IT staff. \
[AI\] (Ken) will contact David Groep about VOMS GUMS. \
[AI\] (Steven) will develop a one-page write-up on attribute aggregation. \
[AI\] (Jim) will check on whether there has been discussion on the CIC list concerning LIGO and the domesticated apps list. \
[AI\] (Heather) will ask U. Chicago people to contribute an academic (intra-institutional) use case to the COmanage use case library. \
[AI\] (Jim) will share ESWN call notes with the COmanage-dev list.

DISCUSSION

Development Report

...

• You can link up one group from one Grouper with a group in another Grouper.  This uses Grouper Web Services.
• This can be push (cron), pull (cron), or incremental (means push cron and real time diffs)
• One Grouper needs WS credentials and privileges to read or update a group in another grouper.
• You need to configure how subject sources in one grouper “map” to subject sources in another grouper.  i.e. in one grouper, you have an identifier attribute in the subject source (e.g. eppn, but could be anything), which maps to the subject API id or identifier in the other Grouper
• If the subject does not exist in the other Grouper, you can optionally configure “addSubjectIfNotExist”, so that a call is triggered to the Grouper External Subject interface to create that external subject.  This is either built-in in the Grouper DB, or a customization to however external subjects are managed at the institution.  Note that customization could be a notification for someone or something to process the new user.
• If there are other attributes required to use the service (e.g. email address), that needs to be self-managed by the user (e.g. in the case of Grouper External Subjects module), or however that is managed at the institution.  If it is a pull type sync, then that attribute might be available via Grouper WS (depending on security).

Wiki Markup\[AI\] Heather will track on a wiki page approaches to sharing metadata between collab platforms.

Next COmanage-Dev Call: Friday, 18-Feb-2011, 2 pm ET

...