...
| Wiki Markup |
|---|
\[AI\] (Heather) will include a discussion of a 3rd COmanage VO as topic for the Tuesday call. \[AI\] (Heather) will schedule an Internet Identity webinar for iPlant IT staff. \[AI\] (Heather) will arrange a meeting with iPlant in TusconTucson. \[AI\] (Heather) will add questions about role transition to the assessment document. \[AI\] (Ken) will contact David Groep about VOMS GUMS. |
...
On Dec 2-3, Heather and Benn met at Caltech with LIGO staff, including ScottK, Melody, Stuart and Warren, to discuss LIGO's COmanage requirements. It was a very productive meeting for all involved. Use cases were reviewed, including scenarios that the LIGO people had not previously been considered. This meeting could possibly be used as a model for engagement with other VOs in the future.
The VOs are interested in assisting, and learning from, each other in this process. ScottK will participate in an upcoming meeting with the iPlant VO.
...
- There is a Kerberos realm that must be dealt with in the short term
- LIGO is LIGO is an identity provider for its participants, though going forward this identity provider role can hopefully be minimized
- The invite problem applies to one subset of the LIGO user space
- LIGO also has the applicant problem/issue, i.e., some people go to the form and apply for access to resources
- The LIGO IdM workflow depends to some extent on how you came in and who approves you
- We are exploring how much of this process should be built into the COmanage software
Q: Is COmanage going to consider using the Grouper external people inviteinvitation capability?
A: Benn: have not made any clear technology commitments.
For LIGO, invite is less than half of the problem. It's called the "enrollment problem" not the "invitation problem"
Ken: We have to diffierent two different VOs between . LIGO and iPlant. Do we want to search for a third VO in terms of engagement? If yes, what characteristics do we want? Perhaps a VO that is just forming would be good. Possibly ESWN?
...
LIGO needs to further explore steps involved when a participant transitions from one state to another (ie.eg. from a post-doc to a researcher).
...
Ken's conversations with iPlant have gone well. There have been some internal timing issues. iPlant has a big Plant Biology meeting Jan 16-19. Most likely a meeting with the COmanage and iPlant folks will happen after that, in last late Jan. or early Feb.
iPlant breaks things into two parts:
...
So an important topic is the mechanics and lifecycle of bringing users in. It will be important for any user to be able to establish a collaboration.
Iplant would like a webinar webinar on Internet Identity for the IT group, including disucssion discussion of integration of OpenIds OpenIDs and SAML etc.
iPlant iPlant has a use case for metered use of applications, possibly including enforced logout. This comes into play for applications/services with a limited number of seats.
...
Benn and Steven have been working with Earth Science Women's Network (ESWN), including conducting a recent conference call that included folks from Penn State. Functionality has been agreed upon. The current focus has been is on the building of a Drupal environment. Drupal will be connected to a federated infastructure infrastructure underneath, based on the COmanage proof of concept.
The ESWN Administrator, Rose, will meet with the ESWNBoard ESWN Board next week. She will have access to an intial cut of an ESWN site that runs in a VM at Penn State, set up by Chris. This will show what functionality will be available. The plan is that the ESWN group will be using COmaange COmanage by Feb. 2011.
It was noted that the work done for ESWN is a great example of what's required to package up a simple COmanage appliance that a group with limited technical skill could pick up and us.
...
The file sharing capability could be of interest to some of our VO'sVOs, especially the need to share large datasets with sensitivity to firewalls. It will be useful to understand more of the use cases and scenarios.
...
MACE is responding to community interest in integrating OpenID and other social network signons identities into federated sign on environments. There are various approaches and there are questions on whether there is a business opportunity for inCommon.
...
Ken referenced a recent Bob Blakely Blakley article revision suggested that OpenID is starting to fail
RL "Bob": OpenID may be starting to fail as an interoperable technology, but many sites still want to get users from Google, Facebook, etc.
...