> 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/keeper-connection-manager/advanced-configuration.md).
# Advanced Configuration
Advanced configuration and custom integration options
### Installing and configuring included extensions
Supported extensions, such as those provided by the Keeper Connection Manager packages, are installed through installing their corresponding packages. If you are using [the keeper/guacamole Docker image,](/keeper-connection-manager/installation/docker-compose-install/keeper-guacamole.md) extensions are automatically installed using the above packages depending on the environment variables provided when the container is first started.
| Extension | Package name | Docker image environment variables |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ---------------------------------- |
| [Active Directory / LDAP support](/keeper-connection-manager/authentication/authenticating-users-with-ldap.md) | `kcm-guacamole-auth-ldap` | `LDAP_*` |
| [Duo two-factor authentication](/keeper-connection-manager/advanced-configuration/guacamole.properties/duo-two-factor-authentication-configuration-properties.md) | `kcm-guacamole-auth-duo` | `DUO_*` |
| [Encrypted JSON authentication](/keeper-connection-manager/using-keeper-connection-manager/dynamic-connections.md) | `kcm-guacamole-auth-json` | `JSON_*` |
| MySQL database support | `kcm-guacamole-auth-jdbc-mysql` | `MYSQL_*` |
| PostgreSQL database support | `kcm-guacamole-auth-jdbc-postgresql` | `POSTGRES_*` |
| SQL Server database support | `kcm-guacamole-auth-jdbc-sqlserver` | `SQLSERVER_*` |
| [TOTP two-factor authentication](/keeper-connection-manager/authentication/using-totp-for-multi-factor-authentication.md) | `kcm-guacamole-auth-totp` | `TOTP_*` |
| [SAML 2.0 / SSO Integration](/keeper-connection-manager/authentication/authenticating-users-with-saml.md) | `kcm-guacamole-auth-saml` | `SAML_*` |
| [OpenID Connect Integration](/keeper-connection-manager/authentication/authenticating-users-with-openid-connect.md) | `kcm-guacamole-auth-openid` | `OPENID_*` |
The Keeper Connection Manager packages for supported extensions will automatically create symbolic links to install themselves and any needed libraries/drivers. You do not need to manually create links, copy files, etc. for the extensions which are provided within the Keeper Connection Manager repository.
### Custom Extensions
The functionality of Keeper Connection Manager can be extended throught the use of custom extensions. [This page](/keeper-connection-manager/custom-extensions.md) describes how to create a custom extension with examples.
---
# 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/keeper-connection-manager/advanced-configuration.md?ask=&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.