> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/keeper-connection-manager/kcm-version-2.22.0.md).

# KCM Version 2.22.0

Below is a summary of all user-facing and administrator-facing changes in the KCM 2.22.0 release.

* License expiration reminder/warning notification
* Support for VT100-style function key / keypad console codes
* Open new RBI tabs/windows within main frame
* Miscellaneous fixes/improvements

## License expiration reminder/warning notification <a href="#license-expiration-reminder-warning-notification" id="license-expiration-reminder-warning-notification"></a>

**KCM-462**: Add grace period on license expiration

KCM now includes an automatic notification that advises users when the overall KCM license is nearing its expiration date:

<figure><img src="https://1549319098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGErxSfzX6xZALob42%2Fuploads%2Fat9DNV6Vyc5PV6pYPD5J%2FScreenshot%202025-11-27%20at%202.02.50%E2%80%AFPM.png?alt=media&#x26;token=95868c5f-4765-4a86-be11-37006c423798" alt=""><figcaption></figcaption></figure>

By default, this notification will appear when the license is expiring within the next week. Administrators can lengthen/shorten this period by setting the `healthcheck-license-grace-period` property (if using the RPMs) or the `HEALTHCHECK_LICENSE_GRACE_PERIOD` environment variable (if using `kcm-setup.run` or the Docker images).

## Support for VT100-style function key / keypad console codes <a href="#support-for-vt100-style-function-key-keypad-console-codes" id="support-for-vt100-style-function-key-keypad-console-codes"></a>

**KCM-460**: Support controlling console codes sent for function keys

Different CLI applications expect different console codes sequences to be sent for function keys (F1, F2, F3, etc.) and numeric keypad keys, but KCM has historically only supported the console code format used by the Linux console. The format used by VT100+ terminals is now supported and may be selected by the administrator when configuring the connection.

## Open new RBI tabs/windows within main frame <a href="#open-new-rbi-tabs-windows-within-main-frame" id="open-new-rbi-tabs-windows-within-main-frame"></a>

**KCM-475**: Implement workaround for lack of tab/window support

RBI does not currently support opening multiple tabs or windows within the same connection. Until this support is added, RBI will now redirect any attempt top open a new tab or window to the main frame, allowing the user to interact. Tab support is coming in 2.23.0.

## Miscellaneous fixes/improvements <a href="#miscellaneous-fixes-improvements" id="miscellaneous-fixes-improvements"></a>

**KCM-466**: RBI autofill using dynamic tokens is not working on an EL9 2.20.1 docker installation

**KCM-476**: Autofill against Google no longer successfully authenticates (HTTP 400)

**KCM-477**: Defunct RBI processes accumulate after termination

**KCM-479**: Healthcheck API causes memory leak

**KCM-480**: RBI autofill fails after certain type of Angular page redirects

**KCM-485**: Add support for accept-language HTTP header in Remote Browser Isolation to ensure that the website content is returned in the desired language.

**KCM-487**: Logins to X fail via RBI

**KCM-507**: Established `kcm-setup.run` is no longer compatible with the latest release of Docker Engine

**KCM-508**: Update RBI to latest Chromium (CVE-2025-13223 and CVE-2025-13224)

***

[Upgrade instructions](/release-notes/enterprise/keeper-connection-manager/upgrading.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/enterprise/keeper-connection-manager/kcm-version-2.22.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.