|
|
|
|
|
Selective AutoLoginIPVersion requirementThe method described in this example only works as described in EZproxy 2.2c (2003-08-14) and later. If you use an earlier version of EZproxy, this will not work as described. OverviewWhen 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. StrategyAutoLoginIP provides a way to have EZproxy provide automatic access without requiring authentication. The main use of this mechanism is to provide branch libraries with access to licensed resources that do not recognize the IP addresses of the branch location. In this example, AutoLoginIP is used to allow remote users to access the OPAC through EZproxy without the users being required to authenticate. Groups can be used to allow different groups of users to have access to different groups of databases. In this example, groups are used to force remote users to authenticate when they try to access licensed databases. config.txt/ezproxy.cfgThese sample lines from config.txt/ezproxy.cfg demonstrate how to place the resources that will require authentication into a separate group from the groups available through AutoLoginIP. This configuration requires EZproxy 2.2c (2003-08-14) or later.
user.txt/ezproxy.usrFor this configuration to work, you must configure EZproxy to associate users who log in with the special MustLogin group that was created above. If you are not using any other group logic in user.txt/ezproxy.usr, then simply make this the first line of your user.txt/ezproxy.usr file:
If you are using Groups with EZproxy, then you must insure your group logic also assigns your users into the MustLogin group. |