EZproxy Order - EN Header Image

Which service are you ordering?*

Price Quote

Do you have a price quote for this service?*


A valid price quote is required to order this product.  

Please request an EZproxy price quote before proceeding. 



terms-and-conditions

Contact Information

Name*
Address*
Secondary Support Contact

Billing Contact Information


An invoice will be generated once the service is ordered and in full production.

Name*
Address*

Technical Questionnaire


Some of the following questions are technical in nature and may require you to collect information from additional departments or resources from within your library in order to complete the questionnaire.  

PLEASE NOTE: This will be the server name / URL for logging in and for EZproxy access. The server name will be inst.idm.oclc.org, where inst will be replaced by your selected server name (for example: ohiostate.idm.oclc.org). If your server name is already in use, your EZproxy implementation manager will notify you and work with you to obtain another server name. Once you have provided this server name, it cannot be changed.
PLEASE NOTE: These are more than likely the same IP address(es) you have shared with your content providers. During the initial configuration, we will provide you with the IP address of your new hosted EZproxy server. Once you have received this IP address, please be sure to register it with your content providers.
Will you proxy your local users, or do you want local users to access database resources directly?
Does your institution currently use EZproxy?

User Authentication 

You probably already have an existing system that can authenticate your users. This might be your automation system, an email system, some form of computer accounts on a system, or a database that can be extracted into a text file.  Please note that not all methods are supported with EZproxy.

What method will be used to authenticate your users for EZproxy? *

Intrusion API Options

EZproxy contains a security feature known as the Intrusion API. Information about the Intrusion API is available in the Intrusion API frequently asked questions. 

If enabled, this new feature triggers a real-time call to a blocklist created by IP-intrusion.org and validated via theIPregistry.org security API that will validate the IP address of the requester. This provides real time protection and greatly reduces the time-consuming and manual process of scanning log files for hacked credentials.

By default, the Intrusion API will not be enabled on your server unless we have your express permission to do so. Enabling this feature will cause EZproxy to send the IP address of the end user to PSI IPV Ltd.

If you’d like to enable the Intrusion API then please confirm we have your permission to enable this feature by indicating which of the two options you’d like to use:

Which OCLC services does your institution currently use?

EZproxy Analytics - implementation questionnaire

We will load 12 months of EZproxy log data for the SPU and ezPAARSE index, while Audit logs will be limited to a 6-month period. This applies if you have been an EZproxy hosted customer for at least that duration.

Audit log data in EZproxy provides a detailed record of user activities, including session start and end times, accessed URLs, and login attempts. This information can be instrumental in understanding user behavior, enhancing security by monitoring for unauthorized access attempts, and complying with institutional policies or legal requirements. However, it's important to note that audit logs may contain personally identifiable information (PII), so careful consideration should be given to privacy concerns and compliance with data protection regulations when handling these logs.

Which other OCLC services does your institution currently use?
Do you want the ability to see usernames and details about the users displayed in your Security Dashboard? (Audit Log data). The default is to see a session variable.*
Without prompting users for authentication, we lack the ability to track user analytics within EZproxy. When users are within the library, do you require them to log in to access resources, even if their IP addresses would normally exempt them from doing so?*
If authentication is not required, you will be unable to gather analytics data at an individual user level.
Are you interested in capturing OnSite traffic in EZproxy? (AutoLoginIP)*
OnSite traffic captures the use of digital resources by patrons directly within the library or on campus, offering insights into resource popularity and usage patterns without requiring individual user login. This data is vital for optimizing resource allocation and enhancing the patron experience.
Would you like to delve deeper into your OnSite traffic by segmenting it into specific zones within the library for more granular insights? This would require unique IP addresses for each distinct library area.*
Does your institution have branches, depts., or other affiliations that you would like to see information on displayed in your Analytics dashboards?*
Do you use user groups in EZproxy to sort users based on criteria such as their department, patron type, or user location (such as a branch or campus)?*
For instance, only users at the main library might have access to Resource A.
Additionally, if you're unsure whether you already have certain groups configured, please don't hesitate to reach out to your implementation manager. They can provide you with this information and assist further.
If you're considering creating groups that haven't been configured before, we ask for a sample user account associated with the specific groups you intend to analyze.
How do your patrons find out which electronic database resources are available for them to access? (Select All that Apply)*

Terms and Conditions

Agreement*
Name*

By submitting this form, you are agreeing to the processing of your personal data to be used as described in our OCLC privacy statement and OCLC cookie notice. 

This hidden field has been added by Attribution to CRM Plugin to store Campaign Name in this Form's submission table
This hidden field has been added by Attribution to CRM Plugin to store Campaign Medium in this Form's submission table
This hidden field has been added by Attribution to CRM Plugin to store Campaign Source in this Form's submission table
This hidden field has been added by Attribution to CRM Plugin to store Campaign Content in this Form's submission table
This hidden field has been added by Attribution to CRM Plugin to store Campaign Term in this Form's submission table
This hidden field has been added by Attribution to CRM Plugin to store GCLID (Google Click Identifier) in this Form's submission table
Progress
Cancel
Confirm