What is the advantage of shib/rewrite proxy over just using the rewrite proxy? This is really only compelling if:
- Shib login is accessible from everywhere
- If vendors provide personalized access using shib. Otherwise, you might as well just go all-rewrite.
How to handle walkins/public machines?
How to bypass need for login for on-campus users (changing the on-campus experience is a political issue for many campuses))
How to get out of maintaining IP addresses?
How to get out of having high level of proxy configuration? Apparently there's an "all through" option for ezproxy, and webvpn does this behavior by default, where we don't have to configure the stuff.
Configurations
Shibboleth
Pilot sites establish access with full range of Shibbolized SP's
Evaluate implementation functionality
Evaluate against standard
Rewrite Proxy
EZProxy
WebVPN
User authentication
Walkins
Restricting resource access to a specific subgroup of users (specific attribute settings) through both ezproxy and shibboleth. (Chicago)
Compatibility
Consortial compatibility with link resolvers, catalogs.
Commercial Resources
Getting set up with vendors (testing out ease of process)
Creation of test matrix
Documentation of activity
Walkthrough of use case scenarios
Accessing shibbolized resources through proxy and bypassing proxy