Differences

This shows you the differences between two versions of the page.

--- ezproxy_maintenance [2022/02/15 20:40]
jmulvaney
+++ ezproxy_maintenance [2023/05/24 13:45]
myoungberg Updated OCLC stanza link
@@ Line 3: / Line 3: @@
 Vendor documentation can be found at [[https://help.oclc.org/Library_Management/EZproxy|EZProxy Support]]. Questions regarding EZProxy should be directed to Jack or Jaime in DRMS and troubleshooting issues can be submitted via DBHelp.
+==== Maintaining the Configuration File (config.txt) ====
+OCLC Created Stanzas can be found here: [[https://help.oclc.org/Library_Management/EZproxy/EZproxy_database_stanzas/Database_stanzas]]
+During the renewals process, stanzas should be checked against the OCLC documentation to make sure that the most recent version is being used. The best way to tell if the stanza doesn't work is trying to access a resource from off campus (or via Opera w/ VPN installed) which will trigger a Need Host page if the stanza no longer works. If a resource is cancelled or ceased and we do not retain post-cancellation/perpetual access, then the stanza should be removed from the config file.
+If you need to create a stanza from scratch, please reference others in the config. or search the EZProxy listserv archives. Consider the following:
+  * Where something is in the file matters. It is read top down. Be sure to stick to alphabetization for easy searching.
+  * When creating a resource configuration stanza, determine whether JavaScript is used.
+  * Leave a note of who created the stanza and when.
+  * Always test whether the stanza you created actually works.
 ==== Basic Changes to Stanzas ====
@@ Line 18: / Line 29: @@
       * The Stanzas are roughly alphabetical, and they are hierarchical. Lines that are higher are given priority over lines that are lower.
       * Trials are always at the end of the file.
-  * To add a new stanza, [[https://help.oclc.org/Library_Management/EZproxy/Database_stanzas|Check OCLC]] or use Google to try and find one that someone else has created.
+  * To add a new stanza, [[https://help.oclc.org/Library_Management/EZproxy/EZproxy_database_stanzas/Database_stanzas|Check OCLC]] or use Google to try and find one that someone else has created.
       * To make edits (like an HTTPS update) add information to existing stanzas.
   * Save the Local copy
@@ Line 40: / Line 51: @@
   * HJ otherserver.publisher.com
   * DJ publisher.com
-==== Maintaining the Configuration File (config.txt) ====
-OCLC Created Stanzas can be found here: [[https://help.oclc.org/Library_Management/EZproxy/Database_stanzas]]
-During the renewals process, stanzas should be checked against the OCLC documentation to make sure that the most recent version is being used. The best way to tell if the stanza doesn't work is trying to access a resource from off campus (or via Opera w/ VPN installed) which will trigger a Need Host page if the stanza no longer works. If a resource is cancelled or ceased and we do not retain post-cancellation/perpetual access, then the stanza should be removed from the config file.
-If you need to create a stanza from scratch, please reference others in the config. or search the EZProxy listserv archives. Consider the following:
-  * Where something is in the file matters. It is read top down. Be sure to stick to alphabetization for easy searching.
-  * When creating a resource configuration stanza, determine whether JavaScript is used.
-  * Leave a note of who created the stanza and when.
-  * Always test whether the stanza you created actually works.
 ==== Monthly Maintenance ====
@@ Line 63: / Line 63: @@
   * Notices of available upgrades to the EZProxy software are announced on the Listserv. Do not be hasty in requesting load of upgrades unless a bug fix is urgently needed. Each upgrade contains all previous upgrades. There is no risk in skipping one. LTS manages the EZProxy server and handles the upgrade process as well as the SSL certificate. If you are unsure of the status of either, check the EZProxy web admin - information about both are listed at the top of the page.
-==== Includes Files ====
+==== Include Files ====
 We are not currently using include files for the config. DRMS wants to explore this further in the future but for now please place all stanzas directly in the config file.
+==== User File ====
+The user file is less complex than the config file and is primarily used to temporary block NetIDs which have become compromised until IT confirms that the patrons password has been reset. For specific instructions on this process see the Licensing Violations document below. When blocking a patron, format as "netid::deny"
+To create temporary usernames/passwords for troubleshooting, use the following format:
+# Context (Name of user, etc.)
+Username:Password
+  * Please always preserve the login for EBSCO, Mount Ida, and the temporary EZproxy troubleshooting password. If publishers ask for credentials try and create a unique login and delete it when they are done.
+The username/password for the EZProxy web admin is configured here. **DO NOT DELETE IT.**
+==== EZProxy Public Pages (Documents) ====
+Patrons primarily experience the EZProxy login page, and may never encounter the various other pages which are mostly reserved for specific EZProxy related errors. These are stored in the "docs" directory of the server. The include the following pages:
+  * login.htm
+      * The main login screen for EZProxy. As of Feb. 2022 it reflects the branding of the library website set to be replaced this summer. Work with LTS to update the branding when the new website becomes available.
+  * loginbu.htm
+      * Patrons see this when their NetID or password fail - usually it is because they are using the @umass domain or have an old password saved in their browser.
+  * loginback.htm
+      * Unclear
+  * logout.htm
+      * Only seen when logging out of the EZProxy web admin.
+  * needhost.htm
+      * When a stanza is missing or no longer works for a specific URL/platform patrons see this page. It includes information on how to report the error and contains information DRMS needs to update the stanza.
+  * menu.htm
+      * This page is rarely seen - occasionally publishers (like Newsbank) will block access due to a compromised NetID and patrons will be redirected here.
+  * suspend.htm
+      * When patrons trip a security rule they are shown this page.
+  * cookie.htm
+      * When patrons block all cookies, they will see this page since EZProxy requires cookies to be enabled to operate correctly.
+  * https.htm
+      * Unclear
+  * survey.htm
+      * This is the mines survey managed by LTS/Assessment. It is turned off as of Feb. 2022.
+==== EZProxy Security Rules ====
+As of version 7.1, rules can be set that when patrons trip them will cause their NetID to be logged and/or blocked. Currently the only rules which will block a patron relate to how many gigabytes of content are download, if a NetID access EZproxy from 4 or more countries, or if they access EZProxy from 20 or more IP addresses. There are additional rules which will log a NetID instead of blocking them.
 ==== License Violation Incidents through proxy ====
 See [[license_violation_procedures|License Violation Procedures]]