Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
add docs
adilson3a82ea67e0b8
diff --git a/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt b/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txtindex 12b1e08757..c28b3a7747 100644--- a/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt+++ b/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt@@ -352,6 +352,9 @@ I(?i)GCP Secret Manager(?i)Google Secret Manager(?i)Go SDK+# Keeper and Commander are product names that are also ordinary nouns.+(?i)Keeper+(?i)Commander# PAM is both the product and a lowercase CLI subcommand.(?i)PAMdiff --git a/docs/.vale/styles/config/vocabularies/Infisical/canonical/accept.txt b/docs/.vale/styles/config/vocabularies/Infisical/canonical/accept.txtindex 78f10c432b..62266d0c3f 100644--- a/docs/.vale/styles/config/vocabularies/Infisical/canonical/accept.txt+++ b/docs/.vale/styles/config/vocabularies/Infisical/canonical/accept.txt@@ -252,6 +252,7 @@ DaytonaDBTAb InitioInitio+Keeper Password Manager# --- Identity ---Oktadiff --git a/docs/api-reference/endpoints/app-connections/keeper/available.mdx b/docs/api-reference/endpoints/app-connections/keeper/available.mdxnew file mode 100644index 0000000000..f2b5d1dcd0--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/available.mdx@@ -0,0 +1,4 @@+---+title: "Available"+openapi: "GET /api/v1/app-connections/keeper/available"+---diff --git a/docs/api-reference/endpoints/app-connections/keeper/create.mdx b/docs/api-reference/endpoints/app-connections/keeper/create.mdxnew file mode 100644index 0000000000..739fc360d9--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/create.mdx@@ -0,0 +1,8 @@+---+title: "Create"+openapi: "POST /api/v1/app-connections/keeper"+---++<Note>+ Check out the configuration docs for [Keeper Connections](/integrations/app-connections/keeper) to learn how to obtain the required credentials.+</Note>diff --git a/docs/api-reference/endpoints/app-connections/keeper/delete.mdx b/docs/api-reference/endpoints/app-connections/keeper/delete.mdxnew file mode 100644index 0000000000..f7fadfde98--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/delete.mdx@@ -0,0 +1,4 @@+---+title: "Delete"+openapi: "DELETE /api/v1/app-connections/keeper/{connectionId}"+---diff --git a/docs/api-reference/endpoints/app-connections/keeper/get-by-id.mdx b/docs/api-reference/endpoints/app-connections/keeper/get-by-id.mdxnew file mode 100644index 0000000000..e259de9849--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/get-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get by ID"+openapi: "GET /api/v1/app-connections/keeper/{connectionId}"+---diff --git a/docs/api-reference/endpoints/app-connections/keeper/get-by-name.mdx b/docs/api-reference/endpoints/app-connections/keeper/get-by-name.mdxnew file mode 100644index 0000000000..fbdac702e4--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/get-by-name.mdx@@ -0,0 +1,4 @@+---+title: "Get by name"+openapi: "GET /api/v1/app-connections/keeper/connection-name/{connectionName}"+---diff --git a/docs/api-reference/endpoints/app-connections/keeper/list.mdx b/docs/api-reference/endpoints/app-connections/keeper/list.mdxnew file mode 100644index 0000000000..1c2bdb2c10--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/list.mdx@@ -0,0 +1,4 @@+---+title: "List"+openapi: "GET /api/v1/app-connections/keeper"+---diff --git a/docs/api-reference/endpoints/app-connections/keeper/update.mdx b/docs/api-reference/endpoints/app-connections/keeper/update.mdxnew file mode 100644index 0000000000..f6e2f332bc--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/keeper/update.mdx@@ -0,0 +1,8 @@+---+title: "Update"+openapi: "PATCH /api/v1/app-connections/keeper/{connectionId}"+---++<Note>+ Check out the configuration docs for [Keeper Connections](/integrations/app-connections/keeper) to learn how to obtain the required credentials.+</Note>diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/create.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/create.mdxnew file mode 100644index 0000000000..70367ada73--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/create.mdx@@ -0,0 +1,4 @@+---+title: "Create"+openapi: "POST /api/v1/secret-syncs/keeper-password-manager"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/delete.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/delete.mdxnew file mode 100644index 0000000000..68e658e381--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/delete.mdx@@ -0,0 +1,4 @@+---+title: "Delete"+openapi: "DELETE /api/v1/secret-syncs/keeper-password-manager/{syncId}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-id.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-id.mdxnew file mode 100644index 0000000000..df55b3a473--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get by ID"+openapi: "GET /api/v1/secret-syncs/keeper-password-manager/{syncId}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-name.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-name.mdxnew file mode 100644index 0000000000..3a2355f660--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-name.mdx@@ -0,0 +1,4 @@+---+title: "Get by name"+openapi: "GET /api/v1/secret-syncs/keeper-password-manager/sync-name/{syncName}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/import-secrets.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/import-secrets.mdxnew file mode 100644index 0000000000..03d2b65dc1--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/import-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Import secrets"+openapi: "POST /api/v1/secret-syncs/keeper-password-manager/{syncId}/import-secrets"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/list.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/list.mdxnew file mode 100644index 0000000000..02b5d16246--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/list.mdx@@ -0,0 +1,4 @@+---+title: "List"+openapi: "GET /api/v1/secret-syncs/keeper-password-manager"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/remove-secrets.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/remove-secrets.mdxnew file mode 100644index 0000000000..53bc9713a1--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/remove-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Remove secrets"+openapi: "POST /api/v1/secret-syncs/keeper-password-manager/{syncId}/remove-secrets"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/sync-secrets.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/sync-secrets.mdxnew file mode 100644index 0000000000..6351eb735f--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/sync-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Sync secrets"+openapi: "POST /api/v1/secret-syncs/keeper-password-manager/{syncId}/sync-secrets"+---diff --git a/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/update.mdx b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/update.mdxnew file mode 100644index 0000000000..b1689277b5--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/keeper-password-manager/update.mdx@@ -0,0 +1,4 @@+---+title: "Update"+openapi: "PATCH /api/v1/secret-syncs/keeper-password-manager/{syncId}"+---diff --git a/docs/docs.json b/docs/docs.jsonindex 39e18f1a06..a2ef3fe048 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -266,6 +266,7 @@"integrations/secret-syncs/heroku","integrations/secret-syncs/humanitec","integrations/secret-syncs/external-infisical",+ "integrations/secret-syncs/keeper-password-manager","integrations/secret-syncs/laravel-forge","integrations/secret-syncs/netlify","integrations/secret-syncs/northflank",@@ -1096,6 +1097,7 @@"integrations/app-connections/hasura-cloud","integrations/app-connections/heroku","integrations/app-connections/humanitec",+ "integrations/app-connections/keeper","integrations/app-connections/kemp-loadmaster","integrations/app-connections/external-infisical","integrations/app-connections/laravel-forge",@@ -2109,6 +2111,18 @@"api-reference/endpoints/app-connections/external-infisical/delete"]},+ {+ "group": "Keeper",+ "pages": [+ "api-reference/endpoints/app-connections/keeper/list",+ "api-reference/endpoints/app-connections/keeper/available",+ "api-reference/endpoints/app-connections/keeper/get-by-id",+ "api-reference/endpoints/app-connections/keeper/get-by-name",+ "api-reference/endpoints/app-connections/keeper/create",+ "api-reference/endpoints/app-connections/keeper/update",+ "api-reference/endpoints/app-connections/keeper/delete"+ ]+ },{"group": "Kemp LoadMaster","pages": [@@ -3599,6 +3613,20 @@"api-reference/endpoints/secret-syncs/external-infisical/remove-secrets"]},+ {+ "group": "Keeper Password Manager",+ "pages": [+ "api-reference/endpoints/secret-syncs/keeper-password-manager/list",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-id",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/get-by-name",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/create",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/update",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/delete",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/sync-secrets",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/import-secrets",+ "api-reference/endpoints/secret-syncs/keeper-password-manager/remove-secrets"+ ]+ },{"group": "Laravel Forge","pages": [diff --git a/docs/images/app-connections/keeper/add-user.png b/docs/images/app-connections/keeper/add-user.pngnew file mode 100644index 0000000000..6893c3a8d2Binary files /dev/null and b/docs/images/app-connections/keeper/add-user.png differdiff --git a/docs/images/app-connections/keeper/connection-created.png b/docs/images/app-connections/keeper/connection-created.pngnew file mode 100644index 0000000000..18a5e2c05eBinary files /dev/null and b/docs/images/app-connections/keeper/connection-created.png differdiff --git a/docs/images/app-connections/keeper/connection-form.png b/docs/images/app-connections/keeper/connection-form.pngnew file mode 100644index 0000000000..796fa2c95fBinary files /dev/null and b/docs/images/app-connections/keeper/connection-form.png differdiff --git a/docs/images/app-connections/keeper/select-keeper-connection.png b/docs/images/app-connections/keeper/select-keeper-connection.pngnew file mode 100644index 0000000000..70c2244ce3Binary files /dev/null and b/docs/images/app-connections/keeper/select-keeper-connection.png differdiff --git a/docs/images/app-connections/keeper/user-2fa-off.png b/docs/images/app-connections/keeper/user-2fa-off.pngnew file mode 100644index 0000000000..64baff6734Binary files /dev/null and b/docs/images/app-connections/keeper/user-2fa-off.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/configure-destination.png b/docs/images/secret-syncs/keeper-password-manager/configure-destination.pngnew file mode 100644index 0000000000..44c0d13264Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/configure-destination.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/configure-details.png b/docs/images/secret-syncs/keeper-password-manager/configure-details.pngnew file mode 100644index 0000000000..b32321f0b4Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/configure-details.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/configure-source.png b/docs/images/secret-syncs/keeper-password-manager/configure-source.pngnew file mode 100644index 0000000000..54cd1e2a29Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/configure-source.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/configure-sync-options.png b/docs/images/secret-syncs/keeper-password-manager/configure-sync-options.pngnew file mode 100644index 0000000000..9259c68515Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/configure-sync-options.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/initial-sync-behavior.png b/docs/images/secret-syncs/keeper-password-manager/initial-sync-behavior.pngnew file mode 100644index 0000000000..7de87b5aa3Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/initial-sync-behavior.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/review-configuration.png b/docs/images/secret-syncs/keeper-password-manager/review-configuration.pngnew file mode 100644index 0000000000..8a3317e606Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/review-configuration.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/select-destination.png b/docs/images/secret-syncs/keeper-password-manager/select-destination.pngnew file mode 100644index 0000000000..13db4c7675Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/select-destination.png differdiff --git a/docs/images/secret-syncs/keeper-password-manager/sync-created.png b/docs/images/secret-syncs/keeper-password-manager/sync-created.pngnew file mode 100644index 0000000000..b000f097d5Binary files /dev/null and b/docs/images/secret-syncs/keeper-password-manager/sync-created.png differdiff --git a/docs/integrations/app-connections/keeper.mdx b/docs/integrations/app-connections/keeper.mdxnew file mode 100644index 0000000000..d7edd06445--- /dev/null+++ b/docs/integrations/app-connections/keeper.mdx@@ -0,0 +1,108 @@+---+title: "Keeper connection"+sidebarTitle: "Keeper"+description: "Learn how to configure a Keeper connection for Infisical."+---++import SetUpCommanderServiceMode from "/snippets/app-connections/keeper/set-up-commander-service-mode.mdx";+import ConnectionFormFields from "/snippets/app-connections/keeper/form-fields.mdx";++A Keeper connection authenticates Infisical to [Keeper Commander Service Mode](https://docs.keeper.io/keeperpam/commander-cli/service-mode-rest-api) with the API key Commander generates. Service Mode is a REST API for Keeper Commander that you run in your own infrastructure. Commander signs in to Keeper as a user you create for Infisical, so Infisical can only reach the shared folders you share with that user.++<Note>+ This guide only authenticates Infisical with Keeper. Once the app connection+ is ready, you can [use it to set up+ integrations](#step-3-configure-integrations).+</Note>++## Prerequisites++- Permission to add users in the Keeper Admin Console+- A host that Infisical can reach over HTTPS++## Step 1: Set up Keeper Commander++Infisical sends commands to Keeper Commander, not to Keeper directly. You run Commander in Service Mode on your own host, signed in as a Keeper user you create for Infisical.++<SetUpCommanderServiceMode />++## Step 2: Create the app connection++Next, create the app connection in Infisical.++<Tip>+ To create the connection using the API, use the [Create Keeper+ Connection](/api-reference/endpoints/app-connections/keeper/create) endpoint.+</Tip>++<View title="Organization-level">+ <Steps>+ <Step>+ In the sidebar, select **Integrations**, then open the **App Connections** tab.++ + </Step>+ <Step>+ Select **Add Connection** and choose **Keeper**.++ + </Step>+ <Step>+ Fill out the form's fields:++ <ConnectionFormFields />++ Then, select **Connect to Keeper**.++ ++ The new connection appears in the **App Connections** tab.++ + </Step>+ </Steps>++</View>++<View title="Project-level">+ <Steps>+ <Step>+ In your Secrets Manager project, select **Integrations** from the sidebar, then open the **App Connections** tab.+ </Step>+ <Step>+ Select **Add Connection** and choose **Keeper**.++ + </Step>+ <Step>+ Fill out the form's fields:++ <ConnectionFormFields />++ Then, select **Connect to Keeper**.++ ++ The new connection appears in the **App Connections** tab.++ + </Step>+ </Steps>++</View>++When you select **Connect to Keeper**, Infisical runs Commander's `whoami` command to check that it can reach Commander and that Commander accepts the API key.++<Check>Your Keeper app connection is ready to use.</Check>++## Step 3: Configure integrations++Now that your Keeper app connection is configured, you can use it to set up the following integrations:++<Card+ title="Keeper Password Manager Secret Sync"+ icon="refresh-cw"+ href="/integrations/secret-syncs/keeper-password-manager"+>+ Sync secrets from Infisical to a Keeper shared folder.+</Card>diff --git a/docs/integrations/secret-syncs/keeper-password-manager.mdx b/docs/integrations/secret-syncs/keeper-password-manager.mdxnew file mode 100644index 0000000000..3b407a91fd--- /dev/null+++ b/docs/integrations/secret-syncs/keeper-password-manager.mdx@@ -0,0 +1,190 @@+---+title: "Keeper Password Manager sync"+sidebarTitle: "Keeper Password Manager"+description: "Learn how to configure a Keeper Password Manager sync for Infisical."+---++import ConnectionFormFields from "/snippets/app-connections/keeper/form-fields.mdx";++A Keeper Password Manager Secret Sync pushes secrets from Infisical into a Keeper shared folder, where the users and teams you share the folder with can read them. Each Infisical secret becomes a login record whose title is the secret's name and whose password field holds the secret's value. The title matches the secret's name unless you customize key names to add a prefix or suffix.++<Note>+ The Keeper Password Manager Secret Sync requires a [Keeper app connection](/integrations/app-connections/keeper). This guide walks you through creating a project-scoped app connection.+</Note>++## Prerequisites++- A [project with secrets configured](/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret)+- Keeper Commander running in Service Mode and its API key (see [Set up Keeper Commander](/integrations/app-connections/keeper#step-1-set-up-keeper-commander))++## Step 1: Configure a shared folder++The sync writes secrets to a Keeper shared folder that the Infisical user can manage. The Infisical user is the Keeper user you created when you [set up Keeper Commander](/integrations/app-connections/keeper#step-1-set-up-keeper-commander).++<Steps>+ <Step>+ In your Keeper vault, choose the shared folder Infisical syncs secrets to. You can use an existing shared folder or create a new one.+ </Step>+ <Step>+ Share the folder with the Infisical user, with these permissions:++ - **Manage Records**: On, so Infisical can create and delete records+ - **Can Edit**: On, so Infisical can update record values+ - **Can Share**: Off+ - **Manage Users**: Off++ With **Can Share** and **Manage Users** off, the Infisical user can't give anyone else access to the synced secrets.++ To share the folder from Commander instead, run this command as a user who manages the folder:++ ```bash+ share-folder -e [email protected] -a grant -p on -o off -d on -s off <folder-uid>+ ```++ If you'll create the sync through the API, note the folder's UID. The API identifies the folder by its UID, not its name.+ </Step>+</Steps>++## Step 2: Set up the sync in Infisical++<Tip>+ To create the sync using the API, use the [Create Keeper Password Manager Sync](/api-reference/endpoints/secret-syncs/keeper-password-manager/create) endpoint.+</Tip>++<Steps>+ <Step>+ In your project, go to **Integrations** and open the **Secret Syncs** tab. Select **+ Add Sync**.++ ++ Then, select the **Keeper Password Manager** sync.++ + </Step>+ <Step>+ Under **Source**, choose which secrets to sync from Infisical:++ - **Environment**: The project environment to retrieve secrets from+ - **Secret Path**: The folder path to retrieve secrets from+ - **Include secrets from all subfolders**: When enabled, also syncs [secrets from every folder under the secret path](/integrations/secret-syncs/overview#include-all-subfolders) (secret names must be unique across those folders)++ ++ <Note>+ Commander reads `${` in a record title as the start of a variable. If any secret at this path has a name that contains `${`, the sync fails without writing any secrets, and the error names each rejected key.+ </Note>++ <Tip>+ If you need to sync secrets from multiple folder locations, use [secret imports](/documentation/platform/secret-reference#secret-imports).+ </Tip>++ Then select **Continue**.+ </Step>+ <Step>+ Under **Destination**, create or select the Keeper app connection the sync will use, then choose the shared folder secrets go to.++ <Tabs>+ <Tab title="Create a new app connection">+ Under **Keeper Connection**, select **Create Connection** in the dropdown, then fill in:++ <ConnectionFormFields />++ Select **Connect to Keeper**. Infisical returns you to the sync form with the new connection selected.++ <Note>+ This creates a connection scoped to the current project. To share the connection across other projects, [create it at the organization level](/integrations/app-connections/keeper#step-2-create-the-app-connection) first, then select it here.+ </Note>+ </Tab>+ <Tab title="Use an existing connection">+ Under **Keeper Connection**, select the app connection you'd like to use.+ </Tab>+ </Tabs>++ - **Shared Folder**: The Keeper shared folder to sync secrets to, chosen from the shared folders you've shared with the Infisical user++ ++ Then select **Continue**.+ </Step>+ <Step>+ Under **Initial Sync Behavior**, choose how Infisical handles login records that already exist in the shared folder on the first sync:++ - **Overwrite Keeper Password Manager**: Infisical imports nothing, and writes its secrets to the shared folder+ - **Import from Keeper, prioritize Infisical**: Infisical first imports the title and password of each login record in the folder; if a secret exists in both places, Infisical keeps its own value+ - **Import from Keeper, prioritize Keeper**: Infisical first imports the title and password of each login record in the folder; if a secret exists in both places, the Keeper value replaces the Infisical value++ If you turned on **Include secrets from all subfolders**, **Overwrite Keeper Password Manager** is the only option.++ ++ Then select **Continue**.+ </Step>+ <Step>+ Under **Sync Options**, choose how secrets are synced:++ - **Prevent secret deletion**: When enabled, Infisical adds and updates login records in the shared folder but never deletes them; enable this if you manage some records in the folder outside of Infisical+ - **Auto-sync on changes**: When enabled, secrets sync to Keeper automatically as the source changes; turn it off to sync manually only+ - **Customize key names**: Adds a prefix or suffix to every synced name, using `{{secretKey}}` for the original name and `{{environment}}` for the environment slug++ <Warning>+ Anyone with access to the shared folder can add login records to it, so a sync can change records that were created outside Infisical. If you don't customize key names, the sync treats every login record in the folder as one it manages:++ - If a login record has the same title as an Infisical secret, the sync overwrites the record's password+ - If **Prevent secret deletion** is off, the sync permanently deletes every login record whose title isn't the name of an Infisical secret++ With customized key names, the sync writes only titles with your prefix or suffix, and deletes only login records whose titles match it.++ Before the first sync, use a shared folder that holds only Infisical's secrets, customize key names, or keep **Prevent secret deletion** on. **Prevent secret deletion** is on by default when you create the sync in the UI, but off unless you set `disableSecretDeletion` when you create it through the API.+ </Warning>++ ++ Then select **Continue**.+ </Step>+ <Step>+ Give the sync a **Name** and an optional **Description**. The name must be slug-friendly.++ ++ Then select **Continue**.+ </Step>+ <Step>+ Review your Keeper Password Manager Sync configuration, then select **Create Sync**.++ ++ <Check>+ The sync is created and appears in the **Secret Syncs** tab. If **Auto-sync on changes** is enabled, it begins syncing secrets to your Keeper shared folder right away.+ </Check>++ + </Step>+</Steps>++## FAQ++<AccordionGroup>+ <Accordion title="Which records in the shared folder does the sync change?">+ The sync only reads and changes login records directly inside the shared folder. It never reads, changes, or deletes other record types or records in subfolders. If two or more login records have the same title, the sync updates the first one and, unless **Prevent secret deletion** is on, deletes the others.+ </Accordion>+ <Accordion title="Why does a sync fail with rate limit errors?">+ Every sync reads the whole shared folder: one request to list the folder, one request per record in the folder, and one more request for each secret that changed. With `-rl 120/minute`, a folder with about 100 records or more can go over the limit. Start the container with a higher `-rl` value, or split your secrets across several shared folders.+ </Accordion>+ <Accordion title="What happens when the Commander session expires?">+ Commander rejects every command, and the sync shows Commander's error. Sign in to Commander on the host again, as in [Set up Keeper Commander](/integrations/app-connections/keeper#step-1-set-up-keeper-commander), then restart the container with `docker restart keeper-service`.+ </Accordion>+ <Accordion title="Why is a shared folder rejected when I save the sync?">+ Commander Service Mode can't run commands on a folder whose UID starts with `-`, so Infisical rejects that folder. [Configure a different shared folder](#step-1-configure-a-shared-folder) for the sync.+ </Accordion>+</AccordionGroup>++## Next steps++<CardGroup cols={2}>+ <Card title="Keeper" icon="plug" href="/integrations/app-connections/keeper">+ Create a Keeper connection at the organization level to share it across projects.+ </Card>+ <Card title="Overview" icon="refresh-cw" href="/integrations/secret-syncs/overview">+ See every destination you can sync secrets to.+ </Card>+</CardGroup>diff --git a/docs/snippets/app-connections/keeper/form-fields.mdx b/docs/snippets/app-connections/keeper/form-fields.mdxnew file mode 100644index 0000000000..1f831415e9--- /dev/null+++ b/docs/snippets/app-connections/keeper/form-fields.mdx@@ -0,0 +1,4 @@+- **Name**: A descriptive name for the connection, such as `keeper-prod`+- **Description** (optional): A note for future reference+- **Instance URL**: The base URL of your Commander Service Mode instance, such as `https://keeper.company.com`, without an `/api` path+- **API Key**: The key you copied when you [set up Keeper Commander](/integrations/app-connections/keeper#step-1-set-up-keeper-commander)diff --git a/docs/snippets/app-connections/keeper/set-up-commander-service-mode.mdx b/docs/snippets/app-connections/keeper/set-up-commander-service-mode.mdxnew file mode 100644index 0000000000..fe17846c30--- /dev/null+++ b/docs/snippets/app-connections/keeper/set-up-commander-service-mode.mdx@@ -0,0 +1,66 @@+<Steps>+ <Step>+ In the Keeper Admin Console, go to **Admin**, open the **Users** tab, and select **Add User**. Enter a **Full Name** and an **Email Address** for the Infisical user, such as `[email protected]`, then select **Add**.++ + </Step>+ <Step>+ Select the edit icon next to the new user to open the user's details, and check that **2FA** is **Off**. Two-factor authentication must stay off for the Infisical user.++ ++ Keeper emails the user an invitation. Accept the invitation and set a master password for the user. The user can't be SSO-only, because Commander signs in with a master password.+ </Step>+ <Step>+ On the host that will run Commander, install Commander and start its shell:++ ```bash+ pip install keepercommander+ keeper shell+ ```++ In the Commander shell, sign in once as the Infisical user, approving the device when Keeper prompts you:++ ```bash+ login --config-file [email protected]+ this-device register+ this-device persistent-login on+ this-device timeout 30d+ ```++ Commander saves the session to `~/.keeper/config.json`. Without `--config-file`, newer Commander versions save the session to the operating system's keychain instead, and the container can't read the keychain. Before you continue, check that `config.json` contains `"config_storage": "file"` and a `device_token`.+ </Step>+ <Step>+ Start Commander in Service Mode with Docker, mounting the `config.json` file from the previous step:++ ```bash+ docker run -d --name keeper-service --restart unless-stopped \+ -p 8900:8900 \+ -v $HOME/.keeper/config.json:/home/commander/.keeper/config.json \+ keeper/commander:latest \+ service-create -p 8900 -f json -q n \+ -c 'whoami,list-sf,ls,get,record-add,record-update,rm' \+ -rl 120/minute -aip '<infisical-ip-addresses>'+ ```++ - `-q n` turns off Commander's request queue, so Commander serves the v1 API that Infisical calls+ - `-c` lists the commands Commander accepts, which are exactly the seven commands Infisical runs+ - `-rl` sets how many requests Commander accepts per minute+ - `-aip` lists the IP addresses allowed to call Commander; set it to the IP addresses Infisical connects from++ For other options, see Keeper's [Docker deployment guide](https://docs.keeper.io/keeperpam/commander-cli/service-mode-rest-api/docker-deployment).++ <Note>+ Infisical must be able to reach Commander at the URL you enter in the connection. Serve Commander over HTTPS with a certificate from a public certificate authority, for example through a reverse proxy in front of port `8900`. Infisical doesn't accept self-signed certificates, and it refuses `localhost` and private IP addresses. If you self-host Infisical and Commander runs on your private network, set [`ALLOW_INTERNAL_IP_CONNECTIONS`](/self-hosting/configuration/envars#param-allow-internal-ip-connections) to `true` on your Infisical instance.+ </Note>+ </Step>+ <Step>+ Find the API key Commander generated in the container logs, on the line that starts with `Generated API key:`:++ ```bash+ docker logs keeper-service+ ```++ Copy the key. You need it to create the connection in Infisical.+ </Step>+</Steps>diff --git a/docs/snippets/catalogs/app-connections.jsx b/docs/snippets/catalogs/app-connections.jsxindex 8d243f0772..1f63cd1104 100644--- a/docs/snippets/catalogs/app-connections.jsx+++ b/docs/snippets/catalogs/app-connections.jsx@@ -660,4 +660,12 @@ export const appConnections = ["Learn how to connect Spacelift to pull secrets from Infisical.",category: "DevOps Tools",},+ {+ name: "Keeper",+ slug: "keeper",+ path: "/integrations/app-connections/keeper",+ description:+ "Learn how to connect Keeper Commander Service Mode to sync secrets from Infisical.",+ category: "Security",+ },];diff --git a/docs/snippets/catalogs/integrations.jsx b/docs/snippets/catalogs/integrations.jsxindex 9266201f09..dfcdab4c79 100644--- a/docs/snippets/catalogs/integrations.jsx+++ b/docs/snippets/catalogs/integrations.jsx@@ -122,4 +122,5 @@ export const integrations = [{ name: "Hasura Cloud", path: "/integrations/secret-syncs/hasura-cloud", description: "Learn how to sync secrets from Infisical to Hasura Cloud.", type: "Secret Sync", tag: "Hosting" },{ name: "Daytona", path: "/integrations/secret-syncs/daytona", description: "Learn how to sync secrets from Infisical to a Daytona organization.", type: "Secret Sync", tag: "DevOps Tools" },{ name: "Devin", path: "/integrations/secret-syncs/devin", description: "Learn how to sync secrets from Infisical to Devin.", type: "Secret Sync", tag: "DevOps Tools" },+ { name: "Keeper Password Manager", path: "/integrations/secret-syncs/keeper-password-manager", description: "Learn how to sync secrets from Infisical to a Keeper shared folder.", type: "Secret Sync", tag: "Security" },];