Skip to main content
OCLC Support

Use different EZproxy login pages for different authentication methods

  1. Last updated
  2. Save as PDF

Symptom

  • If using multiple authentication methods that use the EZproxy login page (like SIP2, III, or Text File), if you want pages different from what is in the login.htm then auth tags can be used to point to web pages customized for each method.

Applies to

  • EZproxy

Resolution

To set EZproxy to point to a custom login page when an auth tag of 'siptag' (https://ezproxy.url/login?auth=siptag), add lines like these to the user.txt.  With this, auth=siptag will tell EZproxy to use loginsip.htm instead of login.htm, and then just use this SIP server when authenticating.

auth=siptag,login=loginsip.htm,loginbu=loginbusip.htm
::auth=siptag,SIP
Host host:port
/SIP

An important piece of coding to add, especially if pointing to a different loginbu.htm, is to make sure the custom login.htm includes the auth tag when it submits.  The first and third lines in this example come from the login.htm from the EZproxy installation; the second line here will keep auth=siptag when submitting. Without this, the auth tag is dropped, then EZproxy will look at all methods in the user.txt, and send to the regular loginbu.htm if incorrect credentials are used.

<form action="/login" method="post">
<input type="hidden" name="auth" value="siptag">
<input type="hidden" name="url" value="^U" />

Additional information

This would not need to be done for authentication methods that do not use the EZproxy but instead send users to that method's login page outside of EZproxy (such as SAML, CAS, CGI)

Page ID

67758