Web Client 1.0 (Legacy; 1.x release series) was the first browser-based interface for Password Depot Enterprise Server and is being replaced by the newly developed Web Client 2.0. This article summarizes the official end-of-support timeline and gives a recommendation for planning your migration.
The timeline at a glance
End of support (EOL): December 31, 2026.
No further development: Web Client 1.0 no longer receives new features; development continues exclusively in Web Client 2.0.
Critical security fixes until EOL: Until December 31, 2026, AceBIT provides fixes for critical security vulnerabilities only for Web Client 1.0.
Migration: Migrating to Web Client 2.0 requires Enterprise Server 19.1.0 or later.
The end of support applies exclusively to Web Client 1.0/1.x – not to the Enterprise Server itself and not to the other Password Depot clients (Windows, macOS, Linux, Android, iOS, browser add-ons).
Recommendation: plan your migration now
Check your server version: Web Client 2.0 requires Enterprise Server as of version 19.1.0 (REST API v2.0). Plan the server update first if you are running an older version.
Test Web Client 2.0: Get a first impression via the online demo at https://web.password-depot.de or your own test deployment. Web Client 2.0 is available in the public GitHub repository
acebit-gmbh/web_client_2– an invitation, as required for the private 1.x repository, is no longer necessary.Plan your authentication methods: With Web Client 2.0, OpenID Connect/Entra ID, Windows SSO (Negotiate), SSPI, and Passkeys (WebAuthn) additionally become available in the browser. Decide which methods you want to enable on the server side.
Complete the migration before December 31, 2026: Deploy Web Client 2.0, inform your users, and then remove the 1.x files from your web server.
Note: Web Client 1.x is coupled to the respective server version and requires a matching release version at every server update (see "Web Client 1.x no longer works after a server update"). It is therefore a good idea to combine the migration to Web Client 2.0 with your next scheduled server update instead of continuing to invest in maintaining the 1.x deployment.
Related topics:
Web Client 1.0 vs. 2.0: Differences and Migration
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