Shibboleth Developers

IMPORTANT E-DIAL PHONE NUMBER HAS CHANGED AS OF Jan 1!

1-866-411-0013 (toll free US/Canada only)
or 1 -800-392-6130 (alternate toll free US/Canada only)

for callers outside the USA/Canada dial 1-734-615-7474 (not free)

Pin # (remains the same): 0142203

Agenda:

1) Startup
      - Roll call, agenda bash
      - Intellectual Property Rights Awareness: Internet2 
Intellectual Property Framework
                (http://members.internet2.edu/intellectualproperty.html)

2) Any outstanding Issues?
        - shib wiki rollout
        - java target, status, what steps would someone follow to use it?
        - potential SunGuard code contribution, reviewing their code.
        - next steps, potential subversion/DAV/shib project
        - others?

3) Additional comments on Howard's Shib-Ping proposal?

4) Discussion -- framework for error handling, error reflection in 
the SP implementation. The v1.2 implementation supports a half-dozen 
or so different error pages, and a templating mechanism that will 
substitute runtime values into the page reflected to the browser 
user. In addition, some information is logged in a) IdP transaction 
and error logs (altho production systems presumably only log real 
errors to the error log), and b) SP transaction and error logs. The 
middleware diagnostics effort has talked about collecting and 
filtering these log files,and providing the ability to search them.

But, how do we expect both IdP and  SP sites to *really* handle 
resolving user problems? What kind of problems *really* surface, and 
at what rate? And what info do  we have to provide, and where do we 
have to provide it, to support the problem resolution effort?

Do campuses want browser users to call the SP site help desks (eg at 
elsevier)? Do they want users to call  the local help desk first? 
What info do campuses need in order to pursue and resolve issues?