EZproxy 7.1 upgrade guide

If running EZproxy 7.0.16 

Actions: 

• Verify that at least 200MB of disk space is available in the EZproxy directory to support the new security rules database 
• Download and install the latest version 

If running a version prior to EZproxy 6.6.2 and using SAML authentication 

These steps apply only to sites both running EZproxy versions prior to 6.6.2 and using SAML authentication.  

Actions: 

• Make a backup of your shibuser.txt file (recommended in case you need to revert) 
• Add encryption and signing options to config.txt 
• Make sure your SAML attribute values are quoted in shibuser.txt 

If running a version prior to EZproxy 6.5.2 

Actions: 

• Retrieve your EZproxy WSKey from OCLC WSKey Management 
• Follow these steps to re-validate your WSKey:
  1. Log onto your EZproxy Server.
  2. Stop EZproxy from running as a service.
  3. Remove EZproxy as a service (ezproxy -sr).
  4. Install your EZproxy WSKey:
     
     Windows Command:
     ezproxy -k 123456789101112
     Linux Command (Must be run as root):
     ./ezproxy -k 123456789101112
     Add EZproxy back as a service(ezproxy -si).
     
     After this has been completed, the message should go away.
  5. Restart EZproxy.
• Enable the IntrusionAPI directive, which provides options to audit or block access from pirate or hacker IP addresses 

If running a version prior to EZproxy 6.4.4 

The Location directive is important to realize the benefits of the new security features in EZproxy 7.1. 

Actions: 

• Follow these steps to update your Location directive 
• A Maxmind account is required to download the updated geolocation file 

If running a version prior to EZproxy 6.0 

Starting with version 6.0, EZproxy moved to an annual subscription model. 

Actions: 

• Request a quote for an EZproxy subscription, hosted by OCLC