After an update of Password Depot Enterprise Server, Web Client 1.0 (Legacy; 1.x release series) frequently reports errors: the login fails, the page stays blank, or individual functions stop responding. In most cases the cause is a version incompatibility: Web Client 1.x is tightly coupled to the REST interface of the respective server version and must be updated to the release version matching the new server version after every server update (example of the version pattern: web client release 1.4.7 for server 18.0.7).
How to update Web Client 1.x
Obtain the matching release version: From the GitHub repository of Web Client 1.x (private repository; access with a GitHub account after invitation, available from support on request), download the release version that matches your new server version.
Extract it to the web server's root directory: Extract the contents of the release archive directly into the root directory (webroot) of your web server – not into a subfolder – and completely replace all files of the old version.
Check the server settings: Under Manage → Server settings → Connections → Supported clients, the Web Client option must be enabled; the REST port (default 8714) must be reachable. For server versions up to 19.0.x, additionally: under Manage → Server settings → General, section REST Server, enter as Origin URL the exact URL through which the Enterprise Server is reached in conjunction with the web client (this option was removed with version 19.1.0).
Clear the browser cache: Browsers often keep the web client's script files in the cache and load a mixture of old and new files after the update. Clear the browser cache or test in an incognito/private window first.
Login fails after the update (Active Directory users)
As of server version 18.0.7, the Enterprise Server strictly validates AD login names (server setting ADStrictNaming in pdserver.ini, enabled by default). If an AD user is rejected after the update despite entering the correct password, use the full login name in the web client's login form – in UPN format (user@company.local) or as COMPANY\user – exactly as the user is stored on the server.
Note: As of server version 19.1.0, the Enterprise Server still provides the REST API v1.0 used by Web Client 1.x alongside the new REST API v2.0; however, the web client version must still match the server version. The session timeout of Web Client 1.x is fixed (the REST server's access token expires after 10 minutes of inactivity) and can only be changed by adjusting a constant in the source code and rebuilding.
Web Client 1.0 is no longer being developed; until the end of support on December 31, 2026, only critical security fixes are provided. An upcoming server update is therefore a good opportunity to migrate to Web Client 2.0 (requires Enterprise Server 19.1.0 or later).
Related topics:
Web Client 1.0 vs. 2.0: Differences and Migration
Which authentication methods does Web Client 1.x support?
End of support for Web Client 1.0: Timeline and recommendation
Configuring the port & HTTPS for the web client