Skip to Content.
Sympa Menu

inc-lib-vendor - RE: [InC-Lib-Vendor] RE: Proquest and InCommon Library Services Collaboration

Subject: InC-Lib-Vendor

List archive

RE: [InC-Lib-Vendor] RE: Proquest and InCommon Library Services Collaboration


Chronological Thread 
  • From: "Balakrishnan, Bhaskaran" <>
  • To: David Kennedy <>
  • Cc: "Roberts, Chad" <>, "Connolly, Chuck" <>, "" <>
  • Subject: RE: [InC-Lib-Vendor] RE: Proquest and InCommon Library Services Collaboration
  • Date: Wed, 29 Jul 2009 08:20:14 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

David:

 

Find below a consolidated list of responses for the 3 major ProQuest platforms that support Shibboleth.

Should you have any follow-up questions, please direct them to Chuck Connolly.

 

I will note that we are presently developing a new platform (See: http://www.libraryjournal.com/article/CA6669069.html), scheduled for general availability in 2010. We may need to revisit these responses then.

 

Best regards,

 

B

Bhaskaran Balakrishnan

Director, Product Development

ProQuest
7200 Wisconsin Ave, Suite 601

Bethesda, MD  20814
U.S.A.

Direct Line:  +1 301.961.6728

Fax:  +1 301.961.6720

www.csa.com | www.proquest.com

 

ProQuest… Start here.

 

 

 

PQ = ProQuest Classic

CH = Chadwyck-Healey

CSA = CSA Illumina

 

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

 

PQ - We request the “eduPersonEntitlement” attribute, but we are able to authenticate with or without a response for that attribute (understanding which institution that the user is coming from is our most important consideration).

CH - We prefer to use the 'eduPersonScopedAffiliation' attribute.  We can also support the 'eduPersonEntitlement' attribute, if needed, but so far no customers have required this.

CSA – Most of our Shibboleth-enabled customers use the 'eduPersonScopedAffiliation' attribute, but a few use the 'eduPersonEntitlement' attribute.

 

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?

 

ALL - No additional services are available beyond basic authentication.

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?

 

PQ - Yes.

CH - Yes – contact ProQuest Technical Support who will generate the WAYFless URLs for the customer.
CSA – Yes – ask ProQuest Technical Support to turn on “failover to Shibboleth”, and you can use the same URL for WAYFless login that you would use for non-Shibboleth login.

 

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

 

PQ - Nothing beyond the content available in ProQuest.

CH - No – we do not provide specific Shibboleth-authenticated links.  To clarify: various Chadwyck-Healey products do contain links out to other resources, such as JSTOR, which support Shibboleth.  However a user following such a link would see a login page, and would have to select the option for Shibboleth authentication, and would then be authenticated (with the Shibboleth single sign-on feature ensuring that there was no need to re-enter their credentials at their identity provider).  We do not provide these external links in any special form which automates the Shibboleth authentication at the external site.

CSA – No, but if anyone has access to Shibboleth-authenticated full text, we would be interested in learning about their user experience.  It is probably similar to what Chadwyck-Healey described.

 

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

PQ - ProQuest Customer Service.

CH - Contact ProQuest Customer Service for initial account setup, or ProQuest Technical Support for subsequent problem resolution.  They will usually provide the library with a URL for our Shibboleth Test Page which is used to perform a sample authentication, and then captures the attributes which the library sends.

CSA – ProQuest Technical Support.

 

 

 

 

 

From: David Kennedy [mailto:]
Sent: Thursday, July 09, 2009 16:32
To: Balakrishnan, Bhaskaran
Cc: Roberts, Chad; Connolly, Chuck;
Subject: Re: [InC-Lib-Vendor] RE: Proquest and InCommon Library Services Collaboration

 


Thank you

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


"Balakrishnan, Bhaskaran" <>

07/09/2009 01:50 PM

To

David Kennedy <>, "Roberts, Chad" <>, "Connolly, Chuck" <>

cc

"" <>

Subject

[InC-Lib-Vendor] RE: Proquest and InCommon Library Services Collaboration

 




David:
 
We presently have 3 platforms, all of which provide Shibboleth authentication services. I will collate the information from all 3 platforms and send that to you – I am targeting next week some time.
 
Best regards,
 
B
Bhaskaran Balakrishnan
Director, Product Development
ProQuest
7200 Wisconsin Ave, Suite 601

Bethesda, MD  20814
U.S.A.

Direct Line:  +1 301.961.6728
Fax:  +1 301.961.6720

www.csa.com | www.proquest.com

 
ProQuest… Start here.
 
From: David Kennedy [mailto:]
Sent:
Thursday, July 09, 2009 09:24
To:
Balakrishnan, Bhaskaran; Roberts, Chad; Connolly, Chuck
Cc:

Subject:
Proquest and InCommon Library Services Collaboration

 

Bhaskaran, Chad, Chuck,


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?

  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?

  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?

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

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


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