There are two generations of the web client for browser access to Password Depot Enterprise Server: Web Client 1.0 (Legacy) – the 1.x release series – and the newly developed Web Client 2.0. Both are web applications that you deploy on your own web server; the browser communicates directly with the REST interface of the Enterprise Server (default port 8714), so sensitive data does not pass through the web server. This article compares the key differences and outlines the migration.
The differences at a glance
Table scrolls sideways
Web Client 1.0 (Legacy) | Web Client 2.0 | |
|---|---|---|
Availability | Private GitHub repository ( | Public GitHub repository |
Server requirement | Enterprise Server with the REST interface enabled (REST API v1.0); a valid SSL certificate is mandatory as of server version 18.0.0 | Enterprise Server version 19.1.0 or later (REST API v2.0) |
Authentication methods | Login form with username and password only (Standard Authentication; AD users in the format | Standard, SSPI (domain credentials), Windows SSO (Negotiate), passkeys (WebAuthn), OpenID Connect, Entra ID |
Version coupling | Tied to the respective server version; each server update requires the matching release version | Communicates exclusively via the REST API v2.0 |
Support status | End of support: December 31, 2026 – no further development; critical security fixes until EOL | Actively developed |
Migrating to Web Client 2.0 (short overview)
Update the Enterprise Server to version 19.1.0 or later (required for the REST API v2.0).
Web client access must be enabled under Manage → Server settings → Connections → Supported clients – this setting applies to 1.x and 2.0 alike.
Download Web Client 2.0 from the public GitHub repository and deploy it as a static web application on your web server; you can predefine the server address and port via the
config.jsonfile.If required, enable additional authentication methods (e.g. OpenID Connect) under Manage → Server settings → Connections → Supported authentications.
After successful testing, remove the 1.x files from your web server, inform your users, and have them clear their browser cache once.
Note: Web Client 1.0 is no longer being developed; until the end of support on December 31, 2026, AceBIT provides critical security fixes only. Migrating to Web Client 2.0 requires Enterprise Server 19.1.0 or later – plan the migration in good time, ideally together with your next server update.
Related topics:
How do I get the Web Client 2.0 and what are the requirements?
Web Client 1.x no longer works after a server update
End of support for Web Client 1.0: Timeline and recommendation