> 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/older-versions/kcm-version-2.13.0.md).

# KCM Version 2.13.0

## New Features

* KSM now supports CAC/PIV authentication
  * For more information, visit [here](/keeper-connection-manager/authentication/piv-cac-smart-cards.md).
* KSM now enables administrators to approve/deny user's ability to authenticate with KSM using SSO
  *  For more information, visit [here](/keeper-connection-manager/authentication/account-approve-deny-workflow.md).

## Improvements

* SAML can now be configured automatically with `kcm-setup.run`
  * Rather than manually editing the `docker-compose.yml` file post installation, administrators can now directly configure their deployment to use SAML for SSO with the `kcm-setup.run` script
* The `extension-priority` property may now be configured with the `EXTENSION_PRIORITY` environment variable. 
  * Users no longer need use the catch-all `ADDITIONAL_GUACAMOLE_PROPERTIES` environment variable to set this.


---

# 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/older-versions/kcm-version-2.13.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.