To test the existing authentication settings in your user.txt file:
| Field | Entry | What this tests |
|---|---|---|
| User | Any username. | Whether the username is valid and if that user has administrative permissions. What groups this user belongs to (if groups are configured). Additional access details. |
| Pass | The password corresponding to the entered username. | Whether the password is valid. If your authentication requires users to enter a password, both username and password must be entered and correct to return a Valid credentials message. |
| URL | A URL to evaluate for access. | Whether the target URL alters the authentication result. This is typically used in combination with the IP field to determine how specific URLs will be handled when accessed from various IP addresses. |
| IP | An IP address from which to test. | How EZproxy would behave if the user's IP address is the one specified. This can help to determine if the starting point URL would be excluded from proxying, included for proxying after requiring authentication, or automatically proxied. If a URL is provided, the information provided is specific to that URL. |
| Auth | Any auth value to use for testing. | Some advanced user.txt files use the auth variable to selectively enable or disable sections of user.txt, especially when multiple authentication methods are in use. Various values can be tested by providing them in this field. |
| III Pin | III pin to test if using the III option Password Both that requires the user's name in the Pass fields and III pin in a separate field. | Whether the III pin combined with the name in the Pass field is valid. This field is NOT used when simply using "Password Pin" with III, nor is it used with any other authentication method. |
| Force Debug | Select if you would like to have debugging messages displayed as the test runs. | Provides additional diagnostic details that may be helpful when determining why a particular authentication is failing. |
The results returned will provide the information detailed in the What this tests column above and can serve as a starting point for making edits to your user.txt file to update your configuration.
This can be useful if you are going to move from one authentication method to another. You do not have to alter your working user.txt file to test the configuration you will have to add for the new method.
To test a new authentication configuration:
The results returned will tell you if the username and password are valid according to the new configuration entered in the text box.
You can also use this page to ensure that the usernames you have configured in either the user.txt file or using a third-party authentication method are working correctly and have been assigned to the correct groups.
If you have already added group configurations to your config.txt and user.txt files, enter a username and password from the group you would like to test, then click Test. Check the test results to see if the username has been assigned to the correct groups in the Assigned groups from the user.txt line.
You can test a new group configuration by entering the user.txt configuration at the bottom of the screen. Make sure you have also added the groups to the config.txt file as well, or the user will not be added to the group. If you are not ready to assign resources to specific groups, you can just add the Group directive and name to the bottom of the config.txt file to test users' membership in the groups. After membership has been confirmed, you can add resources to the groups.
You can also ensure that your third-party authentication method is returning the correct attributes for group membership by entering a username and password that should be assigned to a particular group and checking the test results to ensure they have been assigned to the correct group.