Notes: Conference call 8/7/09
Vendor subgroup minutes:
Attendees:
David Kennedy
Andy Ingham
Fred Zhang
Jonathan Lavigne
Foster Zhang
Kent Percival
Dean Woodbeck
Ann West
notes - Kennedy
Agenda:
- Documenting best practices
-- WAYFless urls
-- authenticated direct links
-- ezproxy hybrid compatible
- eduPersonEntitlement
---
Outcomes / Action Items
[AI] (all) need to document on wiki best practices
[AI] (kennedy) follow up with OCLC on eduPersonEntitlement
[AI] (woodbeck) link from incommon service page to registry of resources
---
Updates:
Ingham has been collating reviewing vendor responses and filling in the gaps in the registry
Documenting best practices:
Decided that it is good idea to create best practices documentation on the wiki. Documentation should link out to UK WAYFless url description and also document the two flavors of WAYFless url that will work with ezproxy (SP session initiator and link from IdP). Documentation should also include definition of authenticated direct links and what it means to be ezproxy hybrid compatible.
Discussed whether we should be including attributes in best practices. We should document what a base set of attributes is that vendors should be compatible with, or at least be able to choose from.
Think that it is still a bit of the wild wild west in terms of standardization. This is good news for this group because there is a lot of work to do.
Our group is well positioned and experienced enough to make best practice recommendations. Ways that we might want to vet best practices within in common community, once we discuss with some individual vendors:
- incommon participants list
- space in the in common wiki
- Internet2 meeting in October in San Antonio
- schedule a webinar through AdobeConnect
eduPersonEntitlement:
We are a little baffled why vendors would want to allow all Shib-authenticated users access to their content without doing attribute-based authorization. Maybe attribute-based authorization is just a little ahead of the curve. We understand that common:1 attribute value was before the standard, and some vendors have not made the switch yet. OCLC should not be implementing their own specific value.
No call next week. Next call with be with whole group in two weeks