Call for Participation: Authority Systems and Tools Ken Klingenstein Director, Internet2 Middleware and Security

Topics  A trajectory for Signet and the Authority Recipe  A trajectory for Grouper  The Call for Participation Goals What institutions need to bring to the table What institutions will walk away with  Next Steps

A trajectory for Signet  Specs  Code  Recipe

A trajectory for Grouper  Specs  Code  GUI

Call for Participation  Will be announced within a month or so (in Member update, mw-announce, etc.)  Looking for 6-8 institutions  Looking for a VO to work with 6-8 institutions  Comes with tea and sympathy, but probably no direct financial support

What institutions could bring  Helping to bring needs and set priorities  Contribute to the recipe through a case study  Maybe have a recipe writer we can hire…  Development energy and clue for Plug-ins (from Peoplesoft SIS, Oracle HR, etc…) Connectors (to SIS, Oracle, WebCT, Darwin Video, etc…) AD vs. LDAP parts Testing and QA Diagnostics  Business process reengineering experiences

What institutions will take away  A signet/grouper that might meet your needs  Publicity  Logowear

What’s Required to Participate  Significant institutional commitment, if not campus-wide adoption  Write a case study, with help  Willingness to raise one’s hand to develop a generalized tool, GUI, component, etc when institutional priorities and community needs are aligned.  Evidence of general middleware infrastructure  Some interesting pathologies

Some schools must apply  If you’ve come to this camp  And are a repeat camp offender  And house the PI of a noted VO  Or are doing BPR  And there is broad institutional commitment  And you find this stuff way cool…