Skip to Content.
Sympa Menu

inc-lib-vendor - AW: [InC-Lib-Vendor] AW: Springer and InCommon Library Services Collaboration

Subject: InC-Lib-Vendor

List archive

AW: [InC-Lib-Vendor] AW: Springer and InCommon Library Services Collaboration


Chronological Thread 
  • From: "Lengwenat, Ulrike, Springer DE" <>
  • To: "David Kennedy" <>
  • Cc: <>
  • Subject: AW: [InC-Lib-Vendor] AW: Springer and InCommon Library Services Collaboration
  • Date: Wed, 15 Jul 2009 14:00:36 +0200

David,

 

This is good to know that I will get back to you as soon as we are ready to test these features.

 

With best regards,

Ulrike

Von: David Kennedy [mailto:]
Gesendet: Dienstag, 14. Juli 2009 20:36
An: Lengwenat, Ulrike, Springer DE
Cc:
Betreff: Re: [InC-Lib-Vendor] AW: Springer and InCommon Library Services Collaboration

 


Ulrike,

Thank you for your response and helping our group.

As you roll out new features in the near future, we have a group of institutions gathered on this list that may be able to help with testing or feedback if you would like.

Thanks
Dave

-----
David Kennedy
Systems Programmer
Perkins Library, Duke University
(919) 613-6831


"Lengwenat, Ulrike, Springer DE" <>

07/13/2009 09:51 AM

To

"David Kennedy" <>

cc

<>

Subject

[InC-Lib-Vendor] AW: Springer and InCommon Library Services Collaboration

 




David,
 
Please find my answers to your questions below.
 
With best regards,
Ulrike Lengwenat
Springer Global Manager Access
 
SpringerLink Operations, eProduct Management & Innovation
Tiergartenstr. 17, D-69121 Heidelberg, Germany
tel + 49 (0) 6221 487 8315


www.springerlink.com
 
P Please don't print this e-mail unless you really need to
Von: David Kennedy [mailto:]
Gesendet:
Donnerstag, 9. Juli 2009 15:54
An:
Lengwenat, Ulrike, Springer DE
Cc:

Betreff:
Springer and InCommon Library Services Collaboration

 

Ulrike,


I am writing you on behalf of the InCommon Library Services Collaboration.


We represent a group of research libraries who are working to expand the use of Shibboleth among members of the InCommon federation. As part of that effort, we are gathering information from vendors about how they have implemented Shibboleth. By making this information more accessible, we hope to make it easier for libraries to use the technology. We also would like to help develop common practices among vendors that would simplify the implementation process for everyone involved and make Shibboleth an attractive option for users.


We think that expanding the use of Shibboleth will help you in various ways:


  1. Provide a more secure means of access than IP authentication.

  2. Provide better tools for identifying who is responsible when breaches occur.

  3. Make it possible for users to take advantage of personalized features on a site without requiring them to open a local account maintained by the vendor.

  4. Help to start moving away from IP-based authentication and the overhead it requires.


We ask that you answer the following questions, as they relate to your products and services:


  1. What are the minimum attributes you require from an Identity Provider for basic Shibboleth authentication?

None, but this may change really soon.

  2. What additional services, if any, do you provide through Shibboleth beyond basic login, for example, personalization. If you do provide additional services, what is required to enable them?

We do not support personalization at this time, but will in the near future.

  3. Do you support "WAYFless" access, that is, access that does not require a user to identify where they are from in order to reach his or her local authentication system?

We do not support ‘WAYFless URLs’ at this time, but will in the near futre.

  4. Do you support direct Shibboleth-authenticated links to resources?

No, this will be implemented at the same time as the WAYFless URLs.

  5. Who should libraries contact if they want to set up Shibboleth access to your site or if they have questions or problems?

for technical issues
For all other issues:


We appreciate your willingness to help us in this effort.


David Kennedy, Duke University

Adam Chandler, Cornell University

Andy Ingham, University of North Carolina, Chapel Hill

Jonathan Lavigne, Stanford University

Kent Percival, University of Guelph

Joy Veronneau, Cornell University

Jason Zavar, OCLC

Fred Zhang, Michigan State University

Foster Zhang, Johns Hopkins University


[please send response email to ]


-----
David Kennedy
Systems Programmer
Perkins Library, Duke University
(919) 613-6831




Archive powered by MHonArc 2.6.16.

Top of Page