Agenda (from I2FMM12 F2F)
sprint11 planning, 0.8 planning
Backlog to get LIGO to prod
LIGO External Collaborator Email Based Enrollment
"Django" Use Case
Find related "clean up" tickets that also need to be resolved
Grouper integration backlog (CO-268, CO-443 through CO-450, etc)
Provisioning backlog
CIFER Group API (CO-99)
—
Tagging 0.7
- drivers: what do we need for ADASS, what do we need for LIGO demo, what do we need for LIGO to start running code
- should the grouper code be a blocker for .7? If possible, yes, though the configuration file that would potentially change the schema should NOT be included in the commit
Functional requirements for .8
- email invitation
- provisioning in to LDAP
- Grouper integration
Notifications will immediately follow as LIGO requirement
LIGO Open Science Center use case
- Scott gets notification from a user requesting that a user see a page in a wiki;
- Scott determines if a CO exists for this use case OR creates a new one
- Scott tells the CO admin (if CO exists); he will have an email/name for the person, will cause the email-enrollment-flow to happen
- email enrollment flow collects name, email address, organization (validity dates would be nice but not necessary)
- if only one name set (not preferred AND name), will need something to populate the name in to both CO and Org identities
- email will go out to the user; user clicks on URL and authenticates (federated)
- need a failure mode that will be understandable to the user, b/c Scott will have to contact each IdP as needed
- Assuming success, user logs in and user gets a message indicating enrollment
- the fact that the person is in the CO must be provisioned in to LDAP
- ePPN, name, CO membership (look like the grouper group provisioning if not actually done through the grouper group provisioning)
- the wiki shouldn't have individual ePPN in the ACL, should have groups
- ePPN, name, CO membership (look like the grouper group provisioning if not actually done through the grouper group provisioning)
LIGO Demo
- more of a status update for Warren and Stuart
- will want some data pre-populated (create CO and adds people)
- will want to show pre-created enrollment flows
- will want to show/change all the labels and names that can be customized - needs LIGO language
- want to show a complex flow and just how easy it is (no new PHP required)
Nothing specific above really ends up on the work list for the COmanage team (though something may shakes out as work starts)
Dates and Timelines
- target 0.8 around 10 November 2012; or at least cover the sprint11 timeframe
- next F2F: LIGO meeting if possible (week of Dec 3) OR January/February