> 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/jp/enterprise/keeper-connection-manager/older-versions/kcm-version-2.9.4.md).

# KCM Version 2.9.4

Released on August 6, 2022

## Features

* **PRIV-149**: Support for Domain parameter in Vault integration for Windows logins\
  See: [Dynamic Tokens (Vault integration)](/keeper-connection-manager/jp/vault-integration/dynamic-tokens.md)
* **PRIV-74**: Added small margin to SSH connection windows
* **PRIV-165**: Accept a one-time token for UI-based KSM configuration
* **PRIV-108**: Added support for multiple KSM applications (at the Connection Group Level)
* **PRIV-157**: Added support for custom LDAP Root Certificate
* **PRIV-160**: Added support for signed SAML requests

## Bug Fixes

* **PRIV-161**: Kubernetes support missing from guacd Docker image
* **PRIV-168**: Add "X-Content-Type-Options" header to SSL termination Docker image
* **PRIV-173**: Update kcm-setup.run to support Amazon Linux 2
* **PRIV-174**: Private key authentication fails for VNC with SFTP file transfer option
* **PRIV-175**: Default CSP ruleset for NGINX image is broken on Safari browsers


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/jp/enterprise/keeper-connection-manager/older-versions/kcm-version-2.9.4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.