Skip to Content.
Sympa Menu

inc-librsvcs - RE: [inc-librsvcs] Reply requested: State of the campus pilots

Subject: InCommon Library Services

List archive

RE: [inc-librsvcs] Reply requested: State of the campus pilots


Chronological Thread 
  • From: "Fleming, Declan" <>
  • To: "Eggleston, Holly" <>, <>
  • Subject: RE: [inc-librsvcs] Reply requested: State of the campus pilots
  • Date: Fri, 21 Mar 2008 08:27:53 -0700

Hi - UCSD's answers:

Campus pilot configuration information(if a subset of functionality
isn't active, put (none)
1. Shib-enabled electronic resources:

Holly - can you answer this one?

2. Proxy server/remote access software used:

In Production: web proxy (intercepting, by the definitions here:
http://en.wikipedia.org/wiki/Proxy_server, as opposed to a reverse
proxy)
In Test: EZProxy, Cisco Web VPN

3. Link resolver software used:

In Production: SFX

4. Shib-enabled library services enabled:

In Test: EZProxy/Shib integration, local digital asset mgt system (each
has been proven, awaiting other issues)

A. Is this pilot configuration being used by patrons (in a production or
real-world beta capacity)?

No.

B. What are your main unresolved issues with this configuration?

Determining the proper method to guide patrons to resources
List of resources?
Redirect everything from the catalog through EZProxy?
What are the SFX implications?

C. What additional Shibboleth functionality could make this better?

Beyond having every vendor Shib compliant, thus removing the link
resolver issues, this doesn't seem to be a Shib problem

D. What supplementary solutions could make this better?



E. If you are using a different configuration for production, what are
the outstanding issues with your current production system and do you
think that shibboleth and the hybrid environment solution(s) proposed so
far could resolve these issues?

Our primary issue with the current situation is the burden placed on the
user to configure the intercepting proxy on their home machines

Another issue is access by valid patrons from machines not on our
network that the patron has no ability to modify (kiosk, locked down
clinic station)- such as adding a VPN or changing proxy settings


F. Other comments/questions

I'm not sure what our objectives as a group are. Some things seem
clear, but immediately raise deeper questions:

Get vendors to add Shib as an authentication option.
What influence do we have over the vendors?
Is the UK more successful at this? Why?
Will this ever be a 100% solution?
How does InCommon work? What are the costs to vendors?

Prove that common reverse proxies can accept Shib credentials.
How do we make the experience as clear as possible to the
patrons?
Is Web VPN also a solution here?

Raise awareness of Shib in US Libraries. I've also heard this stated as
helping show that Shib isn't as difficult as most libraries may think.
Do most campuses have a Shib Single Sign On infrastructure?
Is it at all common that campus libraries, rather than some
central IT, are making Shib/SSO decisions?
How does InCommon work? What are the costs to institutions?

Declan Fleming
UCSD

-----Original Message-----
From: Eggleston, Holly []
Sent: Thursday, March 20, 2008 7:28 AM
To:
Subject: [inc-librsvcs] Reply requested: State of the campus pilots

Hi all -

I'm currently wrapping up a long-standing project, so my apologies for
the delay in following up on Steve's mail. That said, I'm excited to
take an active facilitation role in helping to move this project
forward.

Given the "next steps" that Steve enumerated in his mail, the operative
question seems to be are we ready to recommend best practices, and if
not, what remaining issues need resolution?

I'd like to use this as the primary discussion topic for tomorrow's
phone meeting. To get the ball rolling, I'd appreciate it if folks could
reply back to the list with a brief response to the following questions:

Campus pilot configuration information(if a subset of functionality
isn't active, put (none)
1. Shib-enabled electronic resources:
2. Proxy server/remote access software used:
3. Link resolver softwareused:
4. Shib-enabled library services enabled:

A. Is this pilot configuration being used by patrons (in a production or
real-world beta capacity)?
B. What are your main unresolved issues with this configuration?
C. What additional Shibboleth functionality could make this better?
D. What supplementary solutions could make this better?
E. If you are using a different configuration for production, what are
the outstanding issues with your current production system and do you
think that shibboleth and the hybrid environment solution(s) proposed so
far could resolve these issues?
F. Other comments/questions

I'll send an agenda with discussion questions and connection information
later this afternoon.

Thanks!

Holly


Holly Eggleston
Assistant Department Head, Acquisitions
UCSD Libraries
858.534.9668
858.534.1256 (fax)
(personal)
(licensing and electronic resources)





Archive powered by MHonArc 2.6.16.

Top of Page