UC Identity Management Work Group Meeting - 3/8/2004 - Agenda

1. Review of project goals and timelines.  (See the attached charge to this group.)
2. Review of the current state of campus authentication and enterprise directories, along with projected use cases for the new federated authentication infrastructure.
   
3. Attributes that will be required by UCFY/YBO to identify the user.  These systems currently use the UCnetID to identify users, but SSN is a possible alternative.
4. Selection of technology.  I think most of us are expecting this will be Shibboleth, but we'll need a formal decision.  (See http://shibboleth.internet2.edu.)
5. Solutions to the "Where are you from?" (WAYF) issue.  Will users start with a campus "login" page or browse directly to UCFY/YBO?  Should we use the InCommon WAYF service?
6. Attributes required for access to CDL-licensed databases and eduPerson.  I believe everyone is already targeting eduPerson, so this is probably a small issue.  (See http://middleware.internet2.edu/dir/.)
7. Attribute release policies.  We need agreements on which attributes can be released and under what circumstances.  We also need agreements on the allowable uses of attributes once they're released.
8. (Minimal) standards for intra-campus identity management, registration, etc.  Can we use InCommon as a basis for this?  (See http://incommon.internet2.edu/, particularly the "InCommon Perspectus" that is linked from that page.)
9. Division of labor.  We need to develop a basic understanding of who will be doing what.  Here's a "straw man" proposal: