Latin America and Caribbean

EZproxy 5.4.1 now available

 

The library community's leading authentication and access solution has been enhanced again.

A number of issues have been reported and resolved with the EZproxy 5.4.1 release, available now. Fixes with EZproxy 5.4.1 include the following:

  • The restart function now correctly restarts EZproxy on Windows platforms.
  • The IPC file (named ezproxy.ipc) is now being created on Windows platforms. This resolves the possibility of multiple instances of EZproxy being started on a server out of the same directory.
  • Shibboleth with groups is now completing authentication instead of being presented with logup.htm.
  • Fixed: The limit on number of includeFile entries was inadvertently set much smaller in V5.4. The limits set in V5.4.1 are 4096 include files allowed at a depth of up to 64 nested includes - include files with another include statement.
  • Changed: If EZproxy is restarted and an IPC file exists, EZproxy will now issue a message suggesting you can delete this file if you know EZproxy isn't currently running. Before this change, EZproxy would not start or issue a related message.

Issues anticipated to be fixed in EZproxy 5.5 release later this year:

  • The string concatenation operator is interpreted as a character belonging to the neighboring textual constant rather than as a concatenation operator. If you see this problem, the workaround is to insert a space around the operator. For example, this syntax:

    UserFile("groups/" . login:instNumber.".txt")

    works, while

    UserFile("groups/".login:instNumber.".txt")

    does not.
  • When users authenticate using Shibboleth 1.3, each authentication results in the message: "SAMLResponse no encrypted Assertion elements" being written to the messages.txt file. This message can be ignored and will be removed.
  • EZproxy does not work Shibboleth IdP version 2.3 (on any of our supported Operating Systems). We understand what the issue is and are implementing a change to resolve this issue.

Other notes:

  • Some sites are reporting Shibboleth authentication was not working with EZproxy V5.3 on the Solaris operating system. We have verified the Solaris version of EZproxy V5.4.1 works with our test IdP.  Please note the issue about Shibboleth IdP V2.3 above applies to the Solaris version of EZproxy too.
  • Message "SAML received assertion without a status of success, denying access" logged with a failure to authenticate with Shibboleth. This issue has existed since V5.1d and has been reported with institutions in the UK Access federation. OCLC is currently researching this issue and will either issue an update to EZproxy or describe a configuration method to resolve this problem shortly.

We encourage you to upgrade to EZproxy 5.4 .1 to stay current with the latest features. Please review the enhancements page and upgrade at your earliest convenience.

EZproxy Hosted service is now available

A hosted version of EZproxy is now available. Libraries who subscribe to the hosted version are automatically and seamlessly upgraded with each new release of the service. They also enjoy 24 x 7 x 365 support for off-site authentication of electronic content with no servers or IT infrastructure required. The EZproxy hosted version is currently available in the US, and is planned for wider availability going forward.

Send a message to EZproxy [AT] oclc.org to request a quotation on the hosted service for your institution, and plan to attend the next EZproxy Webinar, scheduled for 17 August 2011, to get all your questions answered about the 5.4 release and how the hosted version could work for your library.