Maxmind logo
The following directives or conditions require the Location directive to be included in config.txt because they reference the IP addresses/geographic locations specified in the directive when commanding EZproxy to perform certain actions: In addition to recording your users’ IP addresses and locations in the audit log, Location is also used as a resource EZproxy checks when carrying out other location-specific, security-related actions as specified by additional directives in your config.txt or user.txt file.
Manually specified IP address location information always overrides the data found in the GeoLite city data. EZproxy can read IP address/geographic information when it is saved in the form of a zipped GeoLite file containing a list of IP addresses/geographies, or it can read individual Location directive statements with IP addresses or ranges that you have manually associated with a specific location. Location associates IP addresses with geographic locations and records that information in your audit log. Location is a position-dependent config.txt directive that must appear after any directives, such as Audit and audit-related directives, that must reference the information from this directive. This directive also allows you to create exceptions to these rules when you have users who fall outside of these broad security settings. Many security directives such as Option BlockCountr圜hange and conditions such as IfRegion, IfCountry, and IfCity rely on the data accompanying Location to block users based on location. In addition to serving as a tool to evaluate security, the location directive is also an important tool in enforcing security. While location alone might not provide you with enough information to determine whether a particular user account has been compromised, it can be a starting point for further investigation. If you know a particular user would not be in a particular location, but their credentials are being used to log in to EZproxy from an unlikely location, you can identify that account as a potential security threat and look into its use in more detail. If a content provider contacts you asking about problem accounts, having this additional information in the audit logs can be one piece of data to help you determine if a particular user's use of EZproxy is legitimate or if that person's account credentials have been compromised. Knowing your users' locations can be valuable when you are examining the security of your EZproxy, and the location directive allows you to both audit and then enforce security settings based on your user location.įrom an auditing standpoint, including the location directive and recording that information in the audit logs allows you to easily identify where your patrons are located when they access EZproxy.
#MAXMIND LOGO HOW TO#
Learn how to use the Location config.txt directive to associate IP addresses with geographic locations in EZproxy.