EZproxy provides many options to customize your software to meet the needs of your institutions. These customizations do not need to be configured for EZproxy to provide your remote users with proxied access to resources; however, these configurations can help you to secure your server, tracks EZproxy usage, and customize your users' experience.
- Create search widgets to proxied resources
- The /form URL allows you to place search forms on public web pages. It is similar to /login, except it expects to receive additional form variables which need to be sent to the remote database. When using the /form URL, the requests of local users are sent directly on to the remote database unproxied, whereas unauthenticated remote users are required to log in first, then their requests are sent on proxied to the database.
- Default web pages
- Many of the web pages presented by EZproxy to remote users can be customized.
- Error pages
- Many of the error pages presented by EZproxy to remote users can be replaced with your own pages.
- EZproxy alerts
- The EZproxy messages.txt file records information every time EZproxy is started or restarted. This file also contains alerts of non-fatal errors. These alerts can be helpful when troubleshooting problems that arise with EZproxy.
- Log files overview
- EZproxy offers institutions multiple customizable log formats to record user activity. These logs can be helpful in identifying levels of proxy usage, security concerns, and general operational details. Customization through directives allows EZproxy administrators to refine what information they receive and how often they receive it.
- Move EZproxy to a new server
- The following is a set of general guidelines to follow when moving EZproxy to a new server. There are several variations of ways in which you might move an EZproxy server.
- OPAC proxying
- If your institution's Online Public Access Catalog (OPAC) contains links to your licensed databases, you may find it convenient to have EZproxy provided proxied access to your OPAC so that it can rewrite these links for remote users.
- Selective AutoLoginIP
- When using AutoLoginIP to provide transparent access for select users, it may be necessary to require users to authenticate when accessing other resources. To reliably intermix AutoLoginIP with forced authentication, it is necessary to place the databases that will require authentication into a separate group. The following demonstrates how to construct such a configuration.