When an EZproxy administrator installs the WSKey for an EZproxy subscription, EZproxy will contact the WSKey server and attempt to validate that key. At this point, several things could happen:
https://authn.sd00.worldcat.org/wskey/authorize.action?service=ezproxy&wskey=WSKeyThe server will return a response about the result of the test and whether you were able to authenticate with the server. If the WSKey is invalid, you will also receive the message, "WSKey is invalid."
The below table will explain the warnings you may see in your messages.txt file and what they mean with regard to your WSKey validation for EZproxy V6.1 and later.
As long as your EZproxy server is able to connect to the WSKey server and validate you key, you should only see the following message in your messages.txt file after startup:
EZproxy license key is valid.
If your EZproxy server is unable to validate your key with the WSKey server, you may see one of the messages in the table below. These messages provide two important pieces of information:
To troubleshoot if you see these messages:
EZproxy has attempted to contact the WSKey server at startup and either:
This does not necessarily mean your WSKey is invalid. EZproxy will continue to attempt to validate the key once an hour.
||Hourly Intervals||After startup, the message above will be recorded, and EZproxy will attempt to contact the WSKey server once an hour. If it cannot connect with the server, or connects with the server and cannot validate your WSKey, this Warning will be recorded in messages.txt.|
If EZproxy is unable to validate your key with the WSKey server during the above warning period, a new Danger message will be recorded in messages.txt.
The startup message above will be recorded, and EZproxy will attempt to contact the WSKey server once an hour. If it cannot connect with the server, or connects with the server and cannot validate your WSKey, this Warning will be recorded in messages.txt.
If EZproxy is unable to validate your key with the WSKey server during the above danger period, a new, more descriptive Danger message will be recorded in messages.txt.
You will see this message for three days while EZproxy makes its final, hourly attempts to validate your license key with the WSKey server before the given date.
If you see this message, your license might be nearing its expiration. If you have confirmed that your EZproxy server can connect to the WSKey server, contact firstname.lastname@example.org to confirm your subscription is current or renew.
If you are currently using EZproxy V6.0 or V6.0.8, EZproxy will validate your WSKey for 3 months and record an expiration date of 3 months from that initial installation in your messages.txt log file. On that date, EZproxy will attempt to revalidate the key with the WSKey server. If it is able to validate the key, you will see a new expiration date 3 months from validation in your messages.txt file upon startup and restart. You can ignore these expiration dates as your WSKey will expire a year from your subscription's start date or you can upgrade to V6.1 or later to receive the messages described above. For more details see Known Issues.
This page last revised: September 30, 2015