> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/connectors/secret-providers/install.md).

# Install

This page describes install the Lenses Secret Providers for Kafka Connect.

{% embed url="<https://github.com/lensesio/secret-provider/releases>" %}
Secret Provider Releases
{% endembed %}

Add the plugin to the worker `classloader` isolation via the **`plugin.path`** option:

```properties
plugin.path=/usr/share/connectors,/opt/secret-providers
```

{% hint style="danger" %}
For **Azure** do not use the classloader isolation (`plugin.path`) that Kafka Connect provides. The Azure SDK uses the default classloader and will not find the HTTP client.
{% endhint %}

## Secret rotation

To allow secret rotation, add **`config.action.reload`** to your Connect workers properties files.

This property accepts one of two options:

1. **none** - No action happens at a connector failure (e.g. it can no longer connect to an external system)
2. **restart** - The work will schedule a restart of the connector

{% hint style="danger" %}
Secrets will only be reloaded if the Connector restarts.
{% endhint %}


---

# 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.lenses.io/latest/connectors/secret-providers/install.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.