Ctrlk
HomepageSystem Status
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deprecation Notices

Important information on your Keeper software

Notice of deprecation for legacy versions

Keeper deprecates older versions of application software listed below. This means they’ll no longer be available from our published sources, and the backend will reject any requests coming from those versions.

Keeper Secrets Manager support for Python version below 3.10

Keeper Secrets Manager KSM CLI v 1.3.0 raised the minimum Python version to 3.10. Python 3.7-3.9 users should stay on v1.2.0

Keeper Secrets Manager support for Python version below 3.9

Keeper Secrets Manager Python SDK v 17.2.0 raised the minimum Python version to 3.9. Python 3.6-3.8 users should stay on v17.1.0

Keeper Secrets Manager Ansible Integration v 1.4.0 raised the minimum Python version to 3.9. Python 3.7-3.8 users should stay on v1.3.0

Keeper Client Applications below 17.0

Keeper client applications with a client version of less than 17.0 are considered deprecated.

This applies to the following applications:

  • Keeper Desktop

  • Mobile Apps

  • Automator

  • On-prem SSO Connect

  • Enterprise Bridge

Keeper has released major security improvements with platform version 17. The new architecture introduces the ability for all software components and clients to apply more robust and faster cryptographic algorithms.

Browser Extensions and mobile apps typically auto-update, unless the function has been specifically disabled. If you disabled automatic updates for any of our applications, we encourage you to perform the updates immediately. Likewise if those applications are being deployed as part of a company managed process, please include them in your nearest maintenance window or update cycle.

Important: The following enterprise software components require a manual upgrade which typically involves minor service downtime, similar to updates you performed in the past for the applications. The upgrade process is the same as in the past and typically involves downloading and installing the latest version.

  • On-prem SSO Connect

  • Enterprise Bridge

If you need assistance with these components, please open a ticket with our support team to schedule the upgrade.

Keeper Connection Manager on EL7

With CentOS 7 having reached end-of-life in June 2024, and with RHEL 7 having reached end-of-maintenance at the same time, KCM will no longer provide EL7 builds. This means that the previous release (KCM 2.19.3) will be the last release with an EL7 build and KCM 2.20.0 will be the first release without EL7 support.

Users that are maintaining RPM-based installations of KCM but are still using RHEL 7, CentOS 7, or another EL7-derivative should upgrade to EL8 or EL9 when possible so that they can upgrade to KCM 2.20.0. Support EL10 will be coming in a future release.

Keeper Desktop 32-bit binary version

The 32-bit Keeper Desktop client application is considered obsolete.

Per Microsoft, starting with the May 2020 Update (Version 2004), new OEM computers are required to use 64-bit builds. A 32-bit application does not benefit from the Windows app-model security since it does not have access to the TPM/Windows Credential Locker for encrypting the device-key and does not support Windows Hello.

Keeper Gateway below 1.5

The Keeper Gateway service with a client version of less than 1.5 are considered deprecated.

If you have any questions, please contact the Keeper support team.

PreviousKeeper Release NotesNextNewsletter

Last updated