Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

docs(integrations): poc for app connections and integrations format revamp (#8028)

Adrian Kahali047b7e930504
diff --git a/docs/documentation/platform/secret-rotation/databricks-service-principal-secret.mdx b/docs/documentation/platform/secret-rotation/databricks-service-principal-secret.mdx
index 540c442971..c103a73530 100644
--- a/docs/documentation/platform/secret-rotation/databricks-service-principal-secret.mdx
+++ b/docs/documentation/platform/secret-rotation/databricks-service-principal-secret.mdx
@@ -3,142 +3,108 @@ title: "Databricks service principal secret"
description: "Learn how to automatically rotate Databricks Service Principal OAuth Secrets."
---
-<Note>
+import ConfigureServicePrincipal from "/snippets/app-connections/databricks/configure-service-principal-for-rotation.mdx";
+import ConnectionFormFields from "/snippets/app-connections/databricks/form-fields.mdx";
+
+Rotate the OAuth client secret of a Databricks service principal on a schedule.
+
+<Info>
**Rotation Type: Dual-Phase**
This rotation maintains two active credential sets with overlapping validity, ensuring zero-downtime during rotation cycles.
+</Info>
+
+<Note>
+ This rotation needs a [Databricks app connection](/integrations/app-connections/databricks). This guide walks you through creating a project-scoped app connection.
</Note>
## Prerequisites
-- Ensure you've configured the service principal for rotation. See [Configure Permissions for Secret Rotation](/integrations/app-connections/databricks#configure-permissions-for-secret-rotation).
-- Ensure your network security policies allow incoming requests from Infisical to this rotation provider, if network restrictions apply.
+- A [project with secrets configured](/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret)
+- Network access from Infisical to your Databricks workspace, if network restrictions apply
+
+## Step 1: Set up in Databricks
+
+Create a service principal Infisical can use to reach the workspace and grant it permission to reset the secrets of every service principal you want to rotate.
+
+<ConfigureServicePrincipal />
+
+## Step 2: Set up the rotation in Infisical
+
+<Tip>
+ To create the rotation using the API, use the [Create Databricks Service Principal Secret Rotation](/api-reference/endpoints/secret-rotations/databricks-service-principal-secret/create) endpoint.
+</Tip>
-## Create a Databricks service principal secret rotation in Infisical
+<Steps>
+ <Step title="Add the rotation" titleSize="h3">
+ In your Secrets Manager project, open the dashboard and select **Add Secret Rotation** from the actions dropdown.
-<Tabs>
- <Tab title="Infisical UI">
- 1. Navigate to your Secrets Manager Project's Dashboard and select **Add Secret Rotation** from the actions dropdown.
![Secrets Manager Dashboard](/images/secret-rotations-v2/generic/add-secret-rotation.png)
- 2. Select the **Databricks Service Principal Secret** option.
+ Then, select the **Databricks Service Principal** rotation:
+
![Select Databricks Service Principal Secret](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-option.png)
+ </Step>
+ <Step title="Configure the app connection" titleSize="h3">
+ Create or select the Databricks app connection the rotation will use.
+
+ <Tabs>
+ <Tab title="Create a new app connection">
+ Under **Databricks Connection**, select **Create Connection**, then choose **Databricks Connection**. Select the **Service Principal** method and complete the form:
+
+ <ConnectionFormFields />
+
+ ![Connect via Databricks service principal](/images/secret-rotations-v2/databricks-service-principal-secret/configure-connection.png)
+
+ Then, select **Connect to Databricks**.
+
+ <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/databricks#step-2-create-the-app-connection) first, then select it here.
+ </Note>
+ </Tab>
+ <Tab title="Use an existing connection">
+ Under **Databricks Connection**, select the app connection you'd like to use.
+ </Tab>
+ </Tabs>
+ </Step>
+ <Step title="Configure the rotation" titleSize="h3">
+ Set the rotation behavior.
- 3. Select the **Databricks Connection** to use and configure the rotation behavior. Then click **Next**.
![Rotation Configuration](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-configuration.png)
- - **Databricks Connection** - the connection that will perform the rotation of the specified service principal's OAuth secret.
- - **Rotation Interval** - the interval, in days, that once elapsed will trigger a rotation.
- - **Rotate At** - the local time of day when rotation should occur once the interval has elapsed.
- - **Auto-Rotation Enabled** - whether secrets should automatically be rotated once the rotation interval has elapsed. Disable this option to manually rotate secrets or pause secret rotation.
+ - **Rotation Interval**: The interval, in days, that once elapsed triggers a rotation.
+ - **Rotate At**: The local time of day when rotation should occur once the interval has elapsed.
+ - **Auto-Rotation Enabled**: When enabled, secrets rotate automatically once the interval elapses. Disable to rotate manually or pause rotation.
+
+ When you're done, select **Next**.
+ </Step>
+ <Step title="Pick the target service principal" titleSize="h3">
+ Select the Databricks service principal whose OAuth secret you want to rotate, then select **Next**.
- 4. Select the Databricks service principal whose OAuth secret you want to rotate. Then click **Next**.
![Rotation Parameters](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-parameters.png)
+ </Step>
+ <Step title="Map the rotated values to secret names" titleSize="h3">
+ Specify the secret names that the client credentials should be mapped to, then select **Next**.
- 5. Specify the secret names that the client credentials should be mapped to. Then click **Next**.
![Rotation Secrets Mapping](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-mapping.png)
- - **Client ID** - the name of the secret that the service principal Client ID will be mapped to.
- - **Client Secret** - the name of the secret that the rotated OAuth Client Secret will be mapped to.
+ - **Client ID**: The name of the secret the service principal Client ID is written to.
+ - **Client Secret**: The name of the secret the rotated OAuth Client Secret is written to.
+ </Step>
+ <Step title="Configure the details" titleSize="h3">
+ Give the rotation a **Name** and an optional **Description**, then select **Next**. The name must be slug-friendly.
- 6. Give your rotation a name and description (optional). Then click **Next**.
![Rotation Details](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-details.png)
+ </Step>
+ <Step title="Review and create" titleSize="h3">
+ Review your configuration, then select **Create Secret Rotation**.
- - **Name** - the name of the secret rotation configuration. Must be slug-friendly.
- - **Description** (optional) - a description of this rotation configuration.
-
- 7. Review your configuration, then click **Create Secret Rotation**.
![Rotation Review](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-review.png)
- 8. Your **Databricks Service Principal Secret** credentials are now available for use via the mapped secrets.
![Rotation Created](/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-created.png)
- </Tab>
- <Tab title="API">
- To create a Databricks Service Principal Secret Rotation, make an API request to the [Create Databricks Service Principal Secret Rotation](/api-reference/endpoints/secret-rotations/databricks-service-principal-secret/create) API endpoint.
-
- ### Sample request
-
- ```bash Request
- curl --request POST \
- --url https://us.infisical.com/api/v2/secret-rotations/databricks-service-principal-secret \
- --header 'Content-Type: application/json' \
- --data '{
- "name": "my-databricks-rotation",
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "description": "my service principal secret rotation",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "environment": "dev",
- "secretPath": "/",
- "isAutoRotationEnabled": true,
- "rotationInterval": 30,
- "rotateAtUtc": {
- "hours": 0,
- "minutes": 0
- },
- "parameters": {
- "servicePrincipalId": "76997828332531",
- "servicePrincipalName": "my-service-principal",
- "clientId": "..."
- },
- "secretsMapping": {
- "clientId": "DATABRICKS_CLIENT_ID",
- "clientSecret": "DATABRICKS_CLIENT_SECRET"
- }
- }'
- ```
-
- ### Sample response
-
- ```bash Response
- {
- "secretRotation": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "name": "my-databricks-rotation",
- "description": "my service principal secret rotation",
- "secretsMapping": {
- "clientId": "DATABRICKS_CLIENT_ID",
- "clientSecret": "DATABRICKS_CLIENT_SECRET"
- },
- "isAutoRotationEnabled": true,
- "activeIndex": 0,
- "folderId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "createdAt": "2023-11-07T05:31:56Z",
- "updatedAt": "2023-11-07T05:31:56Z",
- "rotationInterval": 30,
- "rotationStatus": "success",
- "lastRotationAttemptedAt": "2023-11-07T05:31:56Z",
- "lastRotatedAt": "2023-11-07T05:31:56Z",
- "lastRotationJobId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "nextRotationAt": "2023-11-07T05:31:56Z",
- "connection": {
- "app": "databricks",
- "name": "my-databricks-connection",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "environment": {
- "slug": "dev",
- "name": "Development",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "folder": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "path": "/"
- },
- "rotateAtUtc": {
- "hours": 0,
- "minutes": 0
- },
- "lastRotationMessage": null,
- "type": "databricks-service-principal-secret",
- "parameters": {
- "servicePrincipalId": "76997828332531",
- "servicePrincipalName": "my-service-principal",
- "clientId": "..."
- }
- }
- }
- ```
- </Tab>
-</Tabs>
+
+ <Check>
+ Your Databricks service principal credentials are now available through the mapped secrets. If auto-rotation is enabled, they rotate on your configured schedule.
+ </Check>
+ </Step>
+</Steps>
diff --git a/docs/images/app-connections/1password/app-connection-modal-project.png b/docs/images/app-connections/1password/app-connection-modal-project.png
new file mode 100644
index 0000000000..3104ff6aa0
Binary files /dev/null and b/docs/images/app-connections/1password/app-connection-modal-project.png differ
diff --git a/docs/images/app-connections/1password/app-connection-option-project.png b/docs/images/app-connections/1password/app-connection-option-project.png
new file mode 100644
index 0000000000..86bce0767d
Binary files /dev/null and b/docs/images/app-connections/1password/app-connection-option-project.png differ
diff --git a/docs/images/app-connections/databricks/create-databricks-service-principal-method-project.png b/docs/images/app-connections/databricks/create-databricks-service-principal-method-project.png
new file mode 100644
index 0000000000..7ed652a4a6
Binary files /dev/null and b/docs/images/app-connections/databricks/create-databricks-service-principal-method-project.png differ
diff --git a/docs/images/app-connections/databricks/create-databricks-service-principal-method.png b/docs/images/app-connections/databricks/create-databricks-service-principal-method.png
index 508a5c40be..5ea34a104d 100644
Binary files a/docs/images/app-connections/databricks/create-databricks-service-principal-method.png and b/docs/images/app-connections/databricks/create-databricks-service-principal-method.png differ
diff --git a/docs/images/app-connections/databricks/select-databricks-connection-project.png b/docs/images/app-connections/databricks/select-databricks-connection-project.png
new file mode 100644
index 0000000000..c002bcb69e
Binary files /dev/null and b/docs/images/app-connections/databricks/select-databricks-connection-project.png differ
diff --git a/docs/images/app-connections/databricks/select-databricks-connection.png b/docs/images/app-connections/databricks/select-databricks-connection.png
index c002bcb69e..2888068327 100644
Binary files a/docs/images/app-connections/databricks/select-databricks-connection.png and b/docs/images/app-connections/databricks/select-databricks-connection.png differ
diff --git a/docs/images/app-connections/general/add-connection.png b/docs/images/app-connections/general/add-connection.png
index d46bb9e159..1ba310c41b 100644
Binary files a/docs/images/app-connections/general/add-connection.png and b/docs/images/app-connections/general/add-connection.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/configure-connection.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/configure-connection.png
new file mode 100644
index 0000000000..d1a10fe226
Binary files /dev/null and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/configure-connection.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-configuration.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-configuration.png
index 5b94325d5c..242deb10b9 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-configuration.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-configuration.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-created.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-created.png
index 4ce491b680..de2f32be13 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-created.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-created.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-details.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-details.png
index 7374841eb4..638c990d8c 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-details.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-details.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-mapping.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-mapping.png
index 776ddd18b2..5074ece35b 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-mapping.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-mapping.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-option.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-option.png
index 33f0983a03..7c94b6d1b4 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-option.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-option.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-parameters.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-parameters.png
index 8c4c1dd94a..9ceb524597 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-parameters.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-parameters.png differ
diff --git a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-review.png b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-review.png
index 724b6812db..1cea0bf1ef 100644
Binary files a/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-review.png and b/docs/images/secret-rotations-v2/databricks-service-principal-secret/databricks-service-principal-secret-review.png differ
diff --git a/docs/images/secret-rotations-v2/generic/add-secret-rotation.png b/docs/images/secret-rotations-v2/generic/add-secret-rotation.png
index d8c1867d5c..5fbc1b9775 100644
Binary files a/docs/images/secret-rotations-v2/generic/add-secret-rotation.png and b/docs/images/secret-rotations-v2/generic/add-secret-rotation.png differ
diff --git a/docs/images/secret-syncs/1password/configure-connection.png b/docs/images/secret-syncs/1password/configure-connection.png
new file mode 100644
index 0000000000..32d06f05d2
Binary files /dev/null and b/docs/images/secret-syncs/1password/configure-connection.png differ
diff --git a/docs/images/secret-syncs/1password/configure-destination.png b/docs/images/secret-syncs/1password/configure-destination.png
index 786bd15017..8b7b4a2199 100644
Binary files a/docs/images/secret-syncs/1password/configure-destination.png and b/docs/images/secret-syncs/1password/configure-destination.png differ
diff --git a/docs/images/secret-syncs/1password/configure-details.png b/docs/images/secret-syncs/1password/configure-details.png
index 69ce333e36..e8885a938c 100644
Binary files a/docs/images/secret-syncs/1password/configure-details.png and b/docs/images/secret-syncs/1password/configure-details.png differ
diff --git a/docs/images/secret-syncs/1password/configure-source.png b/docs/images/secret-syncs/1password/configure-source.png
index ee08db72b9..35fdfe089d 100644
Binary files a/docs/images/secret-syncs/1password/configure-source.png and b/docs/images/secret-syncs/1password/configure-source.png differ
diff --git a/docs/images/secret-syncs/1password/configure-sync-options.png b/docs/images/secret-syncs/1password/configure-sync-options.png
index f0b3488e26..fa4bdeba14 100644
Binary files a/docs/images/secret-syncs/1password/configure-sync-options.png and b/docs/images/secret-syncs/1password/configure-sync-options.png differ
diff --git a/docs/images/secret-syncs/1password/review-configuration.png b/docs/images/secret-syncs/1password/review-configuration.png
index 5663e7da29..b1d176f2c6 100644
Binary files a/docs/images/secret-syncs/1password/review-configuration.png and b/docs/images/secret-syncs/1password/review-configuration.png differ
diff --git a/docs/images/secret-syncs/1password/select-option.png b/docs/images/secret-syncs/1password/select-option.png
index a19b8189d3..d0cc324fea 100644
Binary files a/docs/images/secret-syncs/1password/select-option.png and b/docs/images/secret-syncs/1password/select-option.png differ
diff --git a/docs/images/secret-syncs/1password/sync-created.png b/docs/images/secret-syncs/1password/sync-created.png
index fbe8c90d6e..127f2ea979 100644
Binary files a/docs/images/secret-syncs/1password/sync-created.png and b/docs/images/secret-syncs/1password/sync-created.png differ
diff --git a/docs/images/secret-syncs/databricks/configure-connection.png b/docs/images/secret-syncs/databricks/configure-connection.png
new file mode 100644
index 0000000000..00ed1d2529
Binary files /dev/null and b/docs/images/secret-syncs/databricks/configure-connection.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-created.png b/docs/images/secret-syncs/databricks/databricks-created.png
index 829c5196cd..112dcb5bd8 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-created.png and b/docs/images/secret-syncs/databricks/databricks-created.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-destination.png b/docs/images/secret-syncs/databricks/databricks-destination.png
index 8b76f8f659..d1925cff5b 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-destination.png and b/docs/images/secret-syncs/databricks/databricks-destination.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-details.png b/docs/images/secret-syncs/databricks/databricks-details.png
index 71630f158b..c4ecc08948 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-details.png and b/docs/images/secret-syncs/databricks/databricks-details.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-options.png b/docs/images/secret-syncs/databricks/databricks-options.png
index 76890d1833..bafef6fb33 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-options.png and b/docs/images/secret-syncs/databricks/databricks-options.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-review.png b/docs/images/secret-syncs/databricks/databricks-review.png
index e7ff5f6c13..f7d648448c 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-review.png and b/docs/images/secret-syncs/databricks/databricks-review.png differ
diff --git a/docs/images/secret-syncs/databricks/databricks-source.png b/docs/images/secret-syncs/databricks/databricks-source.png
index 74e9e35359..7e56d6141e 100644
Binary files a/docs/images/secret-syncs/databricks/databricks-source.png and b/docs/images/secret-syncs/databricks/databricks-source.png differ
diff --git a/docs/images/secret-syncs/databricks/select-databricks-option.png b/docs/images/secret-syncs/databricks/select-databricks-option.png
index 26f2fd4bdf..69eeac047c 100644
Binary files a/docs/images/secret-syncs/databricks/select-databricks-option.png and b/docs/images/secret-syncs/databricks/select-databricks-option.png differ
diff --git a/docs/integrations/app-connections/1password.mdx b/docs/integrations/app-connections/1password.mdx
index dd23553964..7897dc3e69 100644
--- a/docs/integrations/app-connections/1password.mdx
+++ b/docs/integrations/app-connections/1password.mdx
@@ -4,121 +4,83 @@ sidebarTitle: "1Password"
description: "Learn how to configure a 1Password Connection for Infisical."
---
-## Setup 1Password Connect server
+import DeployConnectServer from "/snippets/app-connections/1password/deploy-connect-server.mdx";
+import ConnectionFormFields from "/snippets/app-connections/1password/form-fields.mdx";
+
+A 1Password connection authenticates Infisical to read and write secrets in your 1Password vaults using a [Connect server](https://developer.1password.com/docs/connect) you deploy in your own infrastructure.
<Note>
- If you already have a Connect Server for your vault you may skip this step.
+ This guide doesn't configure any behavior—it just authenticates Infisical with 1Password. Once the app connection is ready, you can [use it to set up integrations](#step-3-configure-integrations).
</Note>
-<Steps>
- <Step title="Navigate to 'Developer' and select 'Other'">
- ![Developer Page](/images/app-connections/1password/developer-page.png)
- </Step>
- <Step title="Select 'Connect Server'">
- ![Select Connect Server](/images/app-connections/1password/click-connect-server.png)
- </Step>
- <Step title="Configure Connect Server">
- 1. Input a name for your Connect Server
- 2. Select "Choose Vaults" and select the vaults you want to connect
- 3. For each selected vault, select **Edit Access** and **Enable All**
- 4. Select "Add Environment"
-
- ![Configure Connect Server](/images/app-connections/1password/configure-connect-server.png)
- </Step>
- <Step title="Configure Access Token">
- 1. Input a name and expiration for the token
- 2. Click "Choose Vaults" and select the vaults you want to connect
- 3. For each selected vault, click **Edit Access** and **Enable All**
- 4. Click "Issue Token"
-
- ![Set Up Access Token](/images/app-connections/1password/set-up-access-token.png)
- </Step>
- <Step title="Deploy Connect Server">
- Download the Credentials File and set up your Connect Server.
-
- <Note>
- Follow [this guide](https://developer.1password.com/docs/connect/get-started#step-2-deploy-1password-connect-server) to deploy a Connect Server.
- </Note>
-
- Make sure to save the **Access Token** for later use.
-
- ![Deploy Server](/images/app-connections/1password/deploy-server.png)
- </Step>
-</Steps>
-
-## Create 1Password connection in Infisical
-
-<Tabs>
- <Tab title="Infisical UI">
- <Steps>
- <Step title="Navigate to App Connections">
- In your Infisical dashboard, navigate to the **Integrations** tab in the desired project, then select **App Connections**.
-
- ![App Connections Tab](/images/app-connections/general/add-connection.png)
- </Step>
- <Step title="Select 1Password Connection">
- Click the **+ Add Connection** button and select the **1Password Connection** option from the available integrations.
-
- ![Select 1Password Connection](/images/app-connections/1password/app-connection-option.png)
- </Step>
- <Step title="Fill out the 1Password Connection Modal">
- Complete the 1Password Connection form by entering:
- - A descriptive name for the connection
- - An optional description for future reference
- - The URL at which your 1Password Connect Server instance is hosted
- - The Access Token from earlier steps
-
- ![1Password Connection Modal](/images/app-connections/1password/app-connection-modal.png)
- </Step>
- <Step title="Connection Created">
- After clicking Create, your **1Password Connection** is established and ready to use with your Infisical project.
-
- ![1Password Connection Created](/images/app-connections/1password/app-connection-created.png)
- </Step>
- </Steps>
- </Tab>
- <Tab title="API">
- To create an 1Password Connection, make an API request to the [Create 1Password Connection](/api-reference/endpoints/app-connections/1password/create) API endpoint.
-
- ### Sample request
-
- ```bash Request
- curl --request POST \
- --url https://app.infisical.com/api/v1/app-connections/1password \
- --header 'Content-Type: application/json' \
- --data '{
- "name": "my-1password-connection",
- "method": "api-token",
- "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
- "credentials": {
- "instanceUrl": "https://1pass.example.com",
- "apiToken": "<YOUR-API-TOKEN>"
- }
- }'
- ```
-
- ### Sample response
-
- ```bash Response
- {
- "appConnection": {
- "id": "e5d18aca-86f7-4026-a95e-efb8aeb0d8e6",
- "name": "my-1password-connection",
- "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
- "description": null,
- "version": 1,
- "orgId": "6f03caa1-a5de-43ce-b127-95a145d3464c",
- "createdAt": "2025-04-23T19:46:34.831Z",
- "updatedAt": "2025-04-23T19:46:34.831Z",
- "isPlatformManagedCredentials": false,
- "credentialsHash": "7c2d371dec195f82a6a0d5b41c970a229cfcaf88e894a5b6395e2dbd0280661f",
- "app": "1password",
- "method": "api-token",
- "credentials": {
- "instanceUrl": "https://1pass.example.com"
- }
- }
- }
- ```
- </Tab>
-</Tabs>
+## Step 1: Deploy a 1Password Connect server
+
+To sync secrets to a 1Password vault, Infisical needs to authenticate to a Connect server with access to that vault.
+
+<DeployConnectServer />
+
+## Step 2: Create the app connection
+
+Next, create the app connection in Infisical.
+
+<Tip>
+ To create the connection using the API, use the [Create 1Password Connection](/api-reference/endpoints/app-connections/1password/create) endpoint.
+</Tip>
+
+<View title="Organization-level">
+ <Steps>
+ <Step>
+ In the sidebar, select **Organization Settings**, then open the **App Connections** tab.
+
+ ![App Connections Tab](/images/app-connections/general/add-connection.png)
+ </Step>
+ <Step>
+ Select **+ Add Connection** and choose **1Password Connection**.
+
+ ![Select 1Password Connection](/images/app-connections/1password/app-connection-option.png)
+ </Step>
+ <Step>
+ Fill out the form's fields:
+
+ <ConnectionFormFields />
+
+ Then, select **Connect to 1Password**.
+
+ ![1Password Connection Modal](/images/app-connections/1password/app-connection-modal.png)
+ </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 **1Password Connection**.
+
+ ![Select 1Password Connection](/images/app-connections/1password/app-connection-option-project.png)
+ </Step>
+ <Step>
+ Fill out the form's fields:
+
+ <ConnectionFormFields />
+
+ Then, select **Connect to 1Password**.
+
+ ![1Password Connection Modal](/images/app-connections/1password/app-connection-modal-project.png)
+ </Step>
+ </Steps>
+</View>
+
+<Check>
+ Your 1Password app connection is ready to use.
+</Check>
+
+## Step 3: Configure integrations
+
+Now that your 1Password app connection is configured, you can use it to set up the following integrations:
+
+<Card title="1Password Secret Sync" icon="arrows-rotate" href="/integrations/secret-syncs/1password">
+ Sync secrets from Infisical to a 1Password vault.
+</Card>
\ No newline at end of file
diff --git a/docs/integrations/app-connections/databricks.mdx b/docs/integrations/app-connections/databricks.mdx
index c825d89196..c7529c7e1c 100644
--- a/docs/integrations/app-connections/databricks.mdx
+++ b/docs/integrations/app-connections/databricks.mdx
@@ -4,91 +4,86 @@ sidebarTitle: "Databricks"
description: "Learn how to configure a Databricks Connection for Infisical."
---
-Infisical supports the use of [service principals](https://docs.databricks.com/en/admin/users-groups/service-principals.html) to connect with your Databricks workspaces.
-
-## Configure a service principal for Infisical
-
-<Steps>
- <Step title="Databricks Workspace Settings">
- Navigate to your Databricks Workspace **Settings** via the dropdown in the top right.
- ![Workspace Settings Page](/images/app-connections/databricks/workspace-settings.png)
- </Step>
- <Step title="Manage Service Principals">
- Under the **Identity & Access** tab, select the **Manage** button in the **Service Principals** section.
-
- ![Manage Service Principals](/images/app-connections/databricks/manage-service-principals.png)
- </Step>
- <Step title="Service Principal Management">
- Click the **Add Service Principal** button.
-
- ![Add Service Principal](/images/app-connections/databricks/add-service-principal.png)
- </Step>
- <Step title="Add Service Principal">
- Select the **Add New** option and create a service principal for Infisical.
-
- ![Create Service Principal](/images/app-connections/databricks/create-service-principal.png)
- </Step>
- <Step title="Generate Service Principal Secret">
- Click on your new service principal, select the **Secrets** tab and click the **Generate Secret** button.
-
- ![Generate Secret](/images/app-connections/databricks/service-principal-secrets.png)
- </Step>
- <Step title="Service Principal Secret">
- Copy your service principal **Secret** and **Client ID** for use in the following steps.
-
- ![Generate Secret](/images/app-connections/databricks/service-principal-ids.png)
- </Step>
-</Steps>
-
-<Accordion title="Configure Permissions for Secret Rotation">
+import ConfigureServicePrincipal from "/snippets/app-connections/databricks/configure-service-principal.mdx";
+import ConnectionFormFields from "/snippets/app-connections/databricks/form-fields.mdx";
+
+A Databricks connection authenticates Infisical to your Databricks workspace using a [service principal](https://docs.databricks.com/en/admin/users-groups/service-principals.html) that you create for it.
+
+<Note>
+ This guide doesn’t configure any behavior—it just authenticates Infisical with Databricks. Once the app connection is ready, you can [use it to set up integrations](#step-3-configure-integrations).
+</Note>
+
+## Step 1: Configure a service principal in Databricks
+
+<ConfigureServicePrincipal />
+
+## Step 2: Create the app connection
+
+Next, create the app connection in Infisical.
+
+<Tip>
+ To create the connection using the API, use the [Create Databricks Connection](/api-reference/endpoints/app-connections/databricks/create) endpoint.
+</Tip>
+
+<View title="Organization-level">
<Steps>
- <Step title="Add Service Principal to Admin Group">
- Navigate to **Settings** > **Identity & Access** > **Groups** and select the admin group (typically named "admins" or "workspace-admins").
+ <Step>
+ In the sidebar, select **Organization Settings**, then open the **App Connections** tab.
+
+ ![App Connections Tab](/images/app-connections/general/add-connection.png)
+ </Step>
+ <Step>
+ Select **+ Add Connection** and choose **Databricks Connection**.
- ![Admin Group](/images/app-connections/databricks/admin-group.png)
+ ![Select Databricks Connection](/images/app-connections/databricks/select-databricks-connection.png)
+ </Step>
+ <Step>
+ Select the **Service Principal** method, then fill out the form's fields:
+
+ <ConnectionFormFields />
- Click **Add** and select the service principal you created for Infisical to add it to the admin group.
+ Then, select **Connect to Databricks**.
- ![Add to Admin Group](/images/app-connections/databricks/add-to-admin-group.png)
- ![Add to Admin Group Modal](/images/app-connections/databricks/add-to-admin-group-form.png)
+ ![Connect via Databricks service principal](/images/app-connections/databricks/create-databricks-service-principal-method.png)
</Step>
- <Step title="Grant Manage Permission for Target Service Principals">
- For each service principal whose secrets you want to rotate, navigate to **Settings** > **Identity & Access** > **Service Principals** and select the target service principal.
+ </Steps>
+</View>
- ![Select Target Service Principal](/images/app-connections/databricks/select-target-service-principal.png)
+<View title="Project-level">
+ <Steps>
+ <Step>
+ In your Secrets Manager project, select **Integrations** from the sidebar, then open the **App Connections** tab.
</Step>
- <Step title="Open Permissions Tab">
- Click on the **Permissions** tab for the selected service principal. And then click the **Grant access** button to open the permission modal
+ <Step>
+ Select **Add Connection** and choose **Databricks Connection**.
- ![Permissions Tab](/images/app-connections/databricks/permissions-tab.png)
+ ![Select Databricks Connection](/images/app-connections/databricks/select-databricks-connection-project.png)
</Step>
- <Step title="Grant Manage Permission to Infisical Service Principal">
- In the **User, Group or Service Principal** field, select the service principal you created for Infisical. In the **Permission** field, select **Manage** to allow the Infisical service principal to manage credentials and secrets for this service principal. Click **Save** to apply the permissions. Repeat these steps for each service principal whose secrets you want to rotate.
+ <Step>
+ Select the **Service Principal** method, then fill out the form's fields:
+
+ <ConnectionFormFields />
- ![Assign Manage Permission](/images/app-connections/databricks/assign-manage-permission.png)
+ Then, select **Connect to Databricks**.
+
+ ![Connect via Databricks service principal](/images/app-connections/databricks/create-databricks-service-principal-method-project.png)
</Step>
</Steps>
-</Accordion>
-
-## Setup Databricks connection in Infisical
-
-<Steps>
- <Step title="Navigate to App Connections">
- Navigate to the **Integrations** tab in the desired project, then select **App Connections**. ![App Connections
- Tab](/images/app-connections/general/add-connection.png)
- </Step>
- <Step title="Add Connection">
- Select the **Databricks Connection** option from the connection options modal.
- ![Select Databricks
- Connection](/images/app-connections/databricks/select-databricks-connection.png)
- </Step>
- <Step title="Authorize Connection">
- Select the **Service Principal** method, add your **workspace URL** and **service principal credentials**, then select **Connect to
- Databricks**. ![Connect via Databricks
- service principal](/images/app-connections/databricks/create-databricks-service-principal-method.png)
- </Step>
- <Step title="Connection Created">
- Your **Databricks Connection** is now available for use. ![Databricks Service Principal
- Connection](/images/app-connections/databricks/databricks-service-principal-connection.png)
- </Step>
-</Steps>
+</View>
+
+<Check>
+ Your Databricks app connection is ready to use.
+</Check>
+
+## Step 3: Configure integrations
+
+Now that your Databricks app connection is configured, you can use it to set up the following integrations:
+
+<CardGroup cols={2}>
+ <Card title="Databricks secret sync" icon="arrows-rotate" href="/integrations/secret-syncs/databricks">
+ Sync secrets from Infisical to a Databricks secret scope.
+ </Card>
+ <Card title="Databricks service principal secret rotation" icon="key" href="/documentation/platform/secret-rotation/databricks-service-principal-secret">
+ Rotate the OAuth client secret of a Databricks service principal.
+ </Card>
+</CardGroup>
diff --git a/docs/integrations/secret-syncs/1password.mdx b/docs/integrations/secret-syncs/1password.mdx
index b29f90b24f..b1cfe313b4 100644
--- a/docs/integrations/secret-syncs/1password.mdx
+++ b/docs/integrations/secret-syncs/1password.mdx
@@ -3,158 +3,122 @@ title: "1Password sync"
description: "Learn how to configure a 1Password Sync for Infisical."
---
-**Prerequisites:**
-- Create an [1Password Connection](/integrations/app-connections/1password)
-
-<Tabs>
- <Tab title="Infisical UI">
- <Steps>
- <Step title="Add Sync">
- Navigate to **Project** > **Integrations** and select the **Secret Syncs** tab. Select the **Add Sync** button.
-
- ![Secret Syncs Tab](/images/secret-syncs/general/secret-sync-tab.png)
- </Step>
- <Step title="Select '1Password'">
- ![Select 1Password](/images/secret-syncs/1password/select-option.png)
- </Step>
- <Step title="Configure source">
- Configure the **Source** from where secrets should be retrieved, then click **Next**.
-
- ![Configure Source](/images/secret-syncs/1password/configure-source.png)
-
- - **Environment**: The project environment to retrieve secrets from.
- - **Secret Path**: The folder path to retrieve secrets from.
-
- <Tip>
- If you need to sync secrets from multiple folder locations, check out [secret imports](/documentation/platform/secret-reference#secret-imports).
- </Tip>
- </Step>
- <Step title="Configure destination">
- Configure the **Destination** to where secrets should be deployed, then click **Next**.
-
- ![Configure Destination](/images/secret-syncs/1password/configure-destination.png)
-
- - **1Password Connection**: The 1Password Connection to authenticate with.
- - **Vault**: The 1Password vault to sync secrets to.
- - **Value Label**: The label of the 1Password item field that will hold your secret value.
- </Step>
- <Step title="Configure sync options">
- Configure the **Sync Options** to specify how secrets should be synced, then click **Next**.
-
- ![Configure Sync Options](/images/secret-syncs/1password/configure-sync-options.png)
-
- - **Initial Sync Behavior**: Determines how Infisical should resolve the initial sync.
- - **Overwrite Destination Secrets**: Removes any secrets at the destination endpoint not present in Infisical.
- - **Import Secrets (Prioritize Infisical)**: Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over 1Password when keys conflict.
- - **Import Secrets (Prioritize 1Password)**: Imports secrets from the destination endpoint before syncing, prioritizing values from 1Password over Infisical when keys conflict.
- - **Key Schema**: Template that determines how secret names are transformed when syncing, using `{{secretKey}}` as a placeholder for the original secret name and `{{environment}}` for the environment.
+import DeployConnectServer from "/snippets/app-connections/1password/deploy-connect-server.mdx";
+import ConnectionFormFields from "/snippets/app-connections/1password/form-fields.mdx";
+
+A 1Password Secret Sync pushes secrets from Infisical into a 1Password vault. Each Infisical secret becomes a 1Password item whose title matches the secret's key, with the secret value stored in a field of your choice.
+
+<Note>
+ The 1Password Secret Sync requires a [1Password app connection](/integrations/app-connections/1password). 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)
+
+## Step 1: Set up in 1Password
+
+First, deploy a Connect server for the vaults you want Infisical to have access to.
+
+<DeployConnectServer />
+
+## Step 2: Set up the sync in Infisical
+
+<Tip>
+ To create the sync using the API, use the [Create 1Password Sync](/api-reference/endpoints/secret-syncs/1password/create) endpoint.
+</Tip>
+
+<Steps>
+ <Step title="Add the sync" titleSize="h3">
+ In your Infisical project, go to **Integrations** and open the **Secret Syncs** tab. Select **+ Add Sync**.
+
+ ![Secret Syncs Tab](/images/secret-syncs/general/secret-sync-tab.png)
+
+ Then, select the **1Password** sync:
+
+ ![Select 1Password](/images/secret-syncs/1password/select-option.png)
+ </Step>
+ <Step title="Configure the source" titleSize="h3">
+ Configure the **Source** from where secrets should be retrieved in Infisical:
+
+ ![Configure Source](/images/secret-syncs/1password/configure-source.png)
+
+ - **Environment**: The project environment to retrieve secrets from.
+ - **Secret Path**: The folder path to retrieve secrets from.
+
+ <Tip>
+ If you need to sync secrets from multiple folder locations, check out [secret imports](/documentation/platform/secret-reference#secret-imports).
+ </Tip>
+
+ Then select **Continue** to configure the sync's destination.
+ </Step>
+ <Step title="Configure the app connection" titleSize="h3">
+ The sync needs a 1Password [app connection](/integrations/app-connections) to function:
+
+ <Tabs>
+ <Tab title="Create a new app connection">
+ Under **1Password Connection**, select an existing app connection, or select **+ Create New Connection** and complete the form:
+
+ <ConnectionFormFields />
+
+ ![1Password Connection Modal](/images/secret-syncs/1password/configure-connection.png)
+
+ Then, select **Connect to 1Password**.
+
<Note>
- We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.
+ This creates a connection scoped to the current project. To share the connection across other projects, you can [create it at the organization level](/integrations/app-connections/1password#step-2-create-the-app-connection) first, then select it here.
</Note>
- - **Auto-Sync Enabled**: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
- - **Disable Secret Deletion**: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.
- </Step>
- <Step title="Configure details">
- Configure the **Details** of your 1Password Sync, then click **Next**.
-
- ![Configure Details](/images/secret-syncs/1password/configure-details.png)
-
- - **Name**: The name of your sync. Must be slug-friendly.
- - **Description**: An optional description for your sync.
- </Step>
- <Step title="Review configuration">
- Review your 1Password Sync configuration, then click **Create Sync**.
-
- ![Review Configuration](/images/secret-syncs/1password/review-configuration.png)
- </Step>
- <Step title="Sync created">
- If enabled, your 1Password Sync will begin syncing your secrets to the destination endpoint.
-
- ![Sync Created](/images/secret-syncs/1password/sync-created.png)
- </Step>
- </Steps>
- </Tab>
- <Tab title="API">
- To create an **1Password Sync**, make an API request to the [Create 1Password Sync](/api-reference/endpoints/secret-syncs/1password/create) API endpoint.
-
- ### Sample request
-
- ```bash Request
- curl --request POST \
- --url https://app.infisical.com/api/v1/secret-syncs/1password \
- --header 'Content-Type: application/json' \
- --data '{
- "name": "my-1password-sync",
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "description": "an example sync",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "environment": "dev",
- "secretPath": "/my-secrets",
- "isEnabled": true,
- "syncOptions": {
- "initialSyncBehavior": "overwrite-destination"
- },
- "destinationConfig": {
- "vaultId": "...",
- "valueLabel": "value"
- }
- }'
- ```
-
- ### Sample response
-
- ```bash Response
- {
- "secretSync": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "name": "my-1password-sync",
- "description": "an example sync",
- "isEnabled": true,
- "version": 1,
- "folderId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "createdAt": "2023-11-07T05:31:56Z",
- "updatedAt": "2023-11-07T05:31:56Z",
- "syncStatus": "succeeded",
- "lastSyncJobId": "123",
- "lastSyncMessage": null,
- "lastSyncedAt": "2023-11-07T05:31:56Z",
- "importStatus": null,
- "lastImportJobId": null,
- "lastImportMessage": null,
- "lastImportedAt": null,
- "removeStatus": null,
- "lastRemoveJobId": null,
- "lastRemoveMessage": null,
- "lastRemovedAt": null,
- "syncOptions": {
- "initialSyncBehavior": "overwrite-destination"
- },
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "connection": {
- "app": "1password",
- "name": "my-1password-connection",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "environment": {
- "slug": "dev",
- "name": "Development",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "folder": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "path": "/my-secrets"
- },
- "destination": "1password",
- "destinationConfig": {
- "vaultId": "...",
- "valueLabel": "value"
- }
- }
- }
- ```
- </Tab>
-</Tabs>
+ </Tab>
+ <Tab title="Use an existing connection">
+ Under **1Password Connection**, select the app connection you'd like to use.
+ </Tab>
+ </Tabs>
+ </Step>
+ <Step title="Configure the target vault" titleSize="h3">
+ Next, configure the vault where secrets should be deployed:
+
+ ![Configure Destination](/images/secret-syncs/1password/configure-destination.png)
+
+ - **Vault**: The 1Password vault to sync secrets to.
+ - **Value Label**: The label of the 1Password item field that will hold your secret value.
+
+ When you're done, select **Continue**.
+ </Step>
+ <Step title="Configure the sync options" titleSize="h3">
+ Configure the **Sync Options** to specify how secrets should be synced.
+
+ ![Configure Sync Options](/images/secret-syncs/1password/configure-sync-options.png)
+
+ - **Initial Sync Behavior**: How Infisical resolves the initial sync.
+ - **Overwrite Destination Secrets**: Removes any secrets at the destination not present in Infisical.
+ - **Import Secrets (Prioritize Infisical)**: Imports secrets from the destination before syncing, prioritizing values from Infisical when keys conflict.
+ - **Import Secrets (Prioritize 1Password)**: Imports secrets from the destination before syncing, prioritizing values from 1Password when keys conflict.
+ - **Key Schema**: Template that transforms secret names when syncing. Use `{{secretKey}}` for the original secret name and `{{environment}}` for the environment.
+ <Note>
+ We highly recommend using a Key Schema so Infisical only manages the specific keys you intend, keeping everything else untouched.
+ </Note>
+ - **Auto-Sync Enabled**: When enabled, secrets sync automatically as the source changes. Disable to sync manually only.
+ - **Disable Secret Deletion**: When enabled, Infisical does not remove secrets from the destination. Enable this if you intend to manage some secrets manually outside of Infisical.
+
+ When you're done, select **Continue**.
+ </Step>
+ <Step title="Configure the details" titleSize="h3">
+ Give the sync a **Name** and an optional **Description**, then select **Next**. The name must be slug-friendly.
+
+ ![Configure Details](/images/secret-syncs/1password/configure-details.png)
+ </Step>
+ <Step title="Review and create" titleSize="h3">
+ Review your 1Password Sync configuration, then select **Create Sync**.
+
+ ![Review Configuration](/images/secret-syncs/1password/review-configuration.png)
+
+ ![Sync Created](/images/secret-syncs/1password/sync-created.png)
+
+ <Check>
+ The sync is created. If [auto-sync](#configure-the-sync-options) is enabled, it begins syncing your secrets to the selected context right away.
+ </Check>
+ </Step>
+</Steps>
## FAQ
diff --git a/docs/integrations/secret-syncs/databricks.mdx b/docs/integrations/secret-syncs/databricks.mdx
index f1eb7d38fe..b9ad27844c 100644
--- a/docs/integrations/secret-syncs/databricks.mdx
+++ b/docs/integrations/secret-syncs/databricks.mdx
@@ -3,145 +3,126 @@ title: "Databricks sync"
description: "Learn how to configure a Databricks Sync for Infisical."
---
-**Prerequisites:**
+import ConfigureServicePrincipal from "/snippets/app-connections/databricks/configure-service-principal.mdx";
+import ConnectionFormFields from "/snippets/app-connections/databricks/form-fields.mdx";
- - Set up and add secrets to [Infisical Cloud](https://app.infisical.com)
- - Create a [Databricks Connection](/integrations/app-connections/databricks)
+A Databricks Secret Sync pushes secrets from Infisical into a [Databricks secret scope](https://docs.databricks.com/en/security/secrets/secret-scopes.html) that jobs and notebooks in the workspace can read.
+
+<Note>
+ The Databricks Secret Sync requires a [Databricks app connection](/integrations/app-connections/databricks). 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)
+- A Databricks secret scope you want secrets synced into. If you don't have one yet, [create a scope](https://docs.databricks.com/en/security/secrets/secret-scopes.html) in your workspace first.
+
+## Step 1: Set up in Databricks
+
+Create a service principal Infisical can use to reach the workspace.
+
+<ConfigureServicePrincipal />
+
+## Step 2: Set up the sync in Infisical
+
+<Tip>
+ To create the sync using the API, use the [Create Databricks Sync](/api-reference/endpoints/secret-syncs/databricks/create) endpoint.
+</Tip>
+
+<Steps>
+ <Step title="Add the sync" titleSize="h3">
+ In your project, go to **Integrations** and open the **Secret Syncs** tab. Select **+ Add Sync**.
-<Tabs>
- <Tab title="Infisical UI">
- 1. Navigate to **Project** > **Integrations** and select the **Secret Syncs** tab. Select the **Add Sync** button.
![Secret Syncs Tab](/images/secret-syncs/general/secret-sync-tab.png)
- 2. Select the **Databricks** option.
+ Then, select the **Databricks** sync.
+
![Select Databricks](/images/secret-syncs/databricks/select-databricks-option.png)
+ </Step>
+ <Step title="Configure the source" titleSize="h3">
+ Configure the **Source** to specify which secrets to sync from Infisical.
- 3. Configure the **Source** from where secrets should be retrieved, then click **Next**.
![Configure Source](/images/secret-syncs/databricks/databricks-source.png)
- - **Environment**: The project environment to retrieve secrets from.
- - **Secret Path**: The folder path to retrieve secrets from.
+ - **Environment**: The project environment to retrieve secrets from.
+ - **Secret Path**: The folder path to retrieve secrets from.
<Tip>
If you need to sync secrets from multiple folder locations, check out [secret imports](/documentation/platform/secret-reference#secret-imports).
</Tip>
- 4. Configure the **Destination** to where secrets should be deployed, then click **Next**.
- ![Configure Destination](/images/secret-syncs/databricks/databricks-destination.png)
+ Then select **Next** to configure the sync's destination.
+ </Step>
+ <Step title="Configure the app connection" titleSize="h3">
+ Create or select the Databricks app connection the sync will use.
- - **Databricks Connection**: The Databricks Connection to authenticate with.
- - **Scope**: The Databricks secret scope to sync secrets to.
+ <Tabs>
+ <Tab title="Create a new app connection">
+ Under **Databricks Connection**, select **Create Connection** in the dropdown, then choose **Databricks Connection**. Select the **Service Principal** method, then fill in:
- <Note>
- You must create a secret scope in your Databricks workspace prior to configuration. Ensure your service principal has [Write permissions](https://docs.databricks.com/en/security/auth/access-control/index.html#secret-acls) for the specified secret scope.
+ <ConnectionFormFields />
- Infisical recommends creating a designated Databricks secret scope for your sync to prevent removal of secrets not managed by Infisical.
- </Note>
+ ![Connect via Databricks service principal](/images/secret-syncs/databricks/configure-connection.png)
- 5. Configure the **Sync Options** to specify how secrets should be synced, then click **Next**.
- ![Configure Options](/images/secret-syncs/databricks/databricks-options.png)
+ Select **Connect to Databricks**. Infisical returns you to the sync form with the new connection selected.
- - **Initial Sync Behavior**: Determines how Infisical should resolve the initial sync.
- - **Overwrite Destination Secrets**: Removes any secrets at the destination endpoint not present in Infisical.
<Note>
- Databricks does not support importing secrets.
+ 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/databricks#step-2-create-the-app-connection) first, then select it here.
</Note>
- - **Key Schema**: Template that determines how secret names are transformed when syncing, using `{{secretKey}}` as a placeholder for the original secret name and `{{environment}}` for the environment.
+ </Tab>
+ <Tab title="Use an existing connection">
+ Under **Databricks Connection**, select the app connection you'd like to use.
+ </Tab>
+ </Tabs>
+ </Step>
+ <Step title="Configure the target scope" titleSize="h3">
+ Configure the Databricks secret scope where secrets should be deployed.
+
+ ![Configure Destination](/images/secret-syncs/databricks/databricks-destination.png)
+
+ - **Scope**: The Databricks secret scope to sync secrets to.
+
+ <Note>
+ Ensure your service principal has [Write permissions](https://docs.databricks.com/en/security/auth/access-control/index.html#secret-acls) for the specified secret scope. We recommend a designated scope for the sync so it doesn't remove secrets managed elsewhere.
+ </Note>
+
+ When you're done, select **Next**.
+ </Step>
+ <Step title="Configure the sync options" titleSize="h3">
+ Configure the **Sync Options** to specify how secrets should be synced.
+
+ ![Configure Options](/images/secret-syncs/databricks/databricks-options.png)
+
+ - **Initial Sync Behavior**: How Infisical resolves the initial sync.
+ - **Overwrite Destination Secrets**: Removes any secrets at the destination not present in Infisical.
<Note>
- We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.
+ The Databricks Secret Sync doesn't support importing secrets.
</Note>
- - **Auto-Sync Enabled**: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
- - **Disable Secret Deletion**: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.
+ - **Key Schema**: Template that transforms secret names when syncing. Use `{{secretKey}}` for the original secret name and `{{environment}}` for the environment.
+ <Note>
+ Use a **Key Schema** so Infisical only manages the keys that match the schema, leaving other keys untouched.
+ </Note>
+ - **Auto-Sync Enabled**: When enabled, secrets sync automatically as the source changes. Disable to sync manually only.
+ - **Disable Secret Deletion**: When enabled, Infisical doesn't remove secrets from the destination. Enable this if you intend to manage some secrets manually outside of Infisical.
+
+ When you're done, select **Next**.
+ </Step>
+ <Step title="Configure the details" titleSize="h3">
+ Give the sync a **Name** and an optional **Description**. The name must be slug-friendly.
- 6. Configure the **Details** of your Databricks Sync, then click **Next**.
![Configure Details](/images/secret-syncs/databricks/databricks-details.png)
- - **Name**: The name of your sync. Must be slug-friendly.
- - **Description**: An optional description for your sync.
+ Then select **Next**.
+ </Step>
+ <Step title="Review and create" titleSize="h3">
+ Review your Databricks Sync configuration, then select **Create Sync**.
- 7. Review your Databricks Sync configuration, then click **Create Sync**.
![Confirm Configuration](/images/secret-syncs/databricks/databricks-review.png)
- 8. If enabled, your Databricks Sync will begin syncing your secrets to the destination endpoint.
![Sync Secrets](/images/secret-syncs/databricks/databricks-created.png)
- </Tab>
- <Tab title="API">
- To create an **Databricks Sync**, make an API request to the [Create Databricks Sync](/api-reference/endpoints/secret-syncs/databricks/create) API endpoint.
-
- ### Sample request
-
- ```bash Request
- curl --request POST \
- --url https://app.infisical.com/api/v1/secret-syncs/databricks \
- --header 'Content-Type: application/json' \
- --data '{
- "name": "my-databricks-sync",
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "description": "an example sync",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "environment": "dev",
- "secretPath": "/my-secrets",
- "isEnabled": true,
- "syncOptions": {
- "initialSyncBehavior": "overwrite-destination"
- },
- "destinationConfig": {
- "scope": "my-scope"
- }
- }'
- ```
-
- ### Sample response
-
- ```bash Response
- {
- "secretSync": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "name": "my-databricks-sync",
- "description": "an example sync",
- "isEnabled": true,
- "version": 1,
- "folderId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "createdAt": "2023-11-07T05:31:56Z",
- "updatedAt": "2023-11-07T05:31:56Z",
- "syncStatus": "succeeded",
- "lastSyncJobId": "123",
- "lastSyncMessage": null,
- "lastSyncedAt": "2023-11-07T05:31:56Z",
- "importStatus": null,
- "lastImportJobId": null,
- "lastImportMessage": null,
- "lastImportedAt": null,
- "removeStatus": null,
- "lastRemoveJobId": null,
- "lastRemoveMessage": null,
- "lastRemovedAt": null,
- "syncOptions": {
- "initialSyncBehavior": "overwrite-destination"
- },
- "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "connection": {
- "app": "databricks",
- "name": "my-databricks-connection",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "environment": {
- "slug": "dev",
- "name": "Development",
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
- },
- "folder": {
- "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
- "path": "/my-secrets"
- },
- "destination": "databricks",
- "destinationConfig": {
- "scope": "my-scope"
- }
- }
- }
- ```
- </Tab>
-</Tabs>
+ <Check>
+ The sync is created. If auto-sync is enabled, it begins syncing secrets to the selected Databricks secret scope right away.
+ </Check>
+ </Step>
+</Steps>
diff --git a/docs/snippets/app-connections/1password/deploy-connect-server.mdx b/docs/snippets/app-connections/1password/deploy-connect-server.mdx
new file mode 100644
index 0000000000..1c14af6530
--- /dev/null
+++ b/docs/snippets/app-connections/1password/deploy-connect-server.mdx
@@ -0,0 +1,36 @@
+<Info>
+ If you already have a Connect server for your vault, you can skip this step.
+</Info>
+
+<Steps>
+ <Step title="Create a Connect server" titleSize="h3">
+ In 1Password, open the **Developer** section and select **Other**.
+
+ ![Developer Page](/images/app-connections/1password/developer-page.png)
+
+ Then, select **Create a Connect Server**.
+
+ ![Select Connect Server](/images/app-connections/1password/click-connect-server.png)
+ </Step>
+ <Step title="Configure the Connect server" titleSize="h3">
+ In the **Environment Name** field, enter a name for the Connect server. Then, select **Choose Vaults** and pick the vaults you want Infisical to reach:
+
+ ![Configure Connect Server](/images/app-connections/1password/configure-connect-server.png)
+
+ For each vault, select **Edit Access** > **Enable All**. When you're done, select **Add Environment**.
+ </Step>
+ <Step title="Set up an access token" titleSize="h3">
+ Infisical needs an access token to authenticate with the Connect server and sync your secrets.
+
+ Set a name and expiration for the token in the **Token Name** and **Expires After** fields. Then, select **Choose Vaults** and pick the vaults you want Infisical to have access to:
+
+ ![Set Up Access Token](/images/app-connections/1password/set-up-access-token.png)
+
+ For each vault, select **Edit Access** > **Enable All**. When you're done, select **Issue Token**.
+ </Step>
+ <Step title="Deploy the Connect server" titleSize="h3">
+ Download the credentials file, then follow [1Password's deployment guide](https://developer.1password.com/docs/connect/get-started#step-2-deploy-1password-connect-server) to bring the server up. Save the **Access Token** you were shown; you'll paste it into Infisical in the next section.
+
+ ![Deploy Server](/images/app-connections/1password/deploy-server.png)
+ </Step>
+</Steps>
diff --git a/docs/snippets/app-connections/1password/form-fields.mdx b/docs/snippets/app-connections/1password/form-fields.mdx
new file mode 100644
index 0000000000..90cc9b4dcb
--- /dev/null
+++ b/docs/snippets/app-connections/1password/form-fields.mdx
@@ -0,0 +1,4 @@
+- **Name**: A descriptive name for the connection.
+- **Description** (optional): A note for future reference.
+- **Instance URL**: The URL where your 1Password Connect server is hosted.
+- **API Token**: The access token you copied when [deploying your 1Password Connect server](#deploy-the-connect-server)
\ No newline at end of file
diff --git a/docs/snippets/app-connections/databricks/configure-service-principal-for-rotation.mdx b/docs/snippets/app-connections/databricks/configure-service-principal-for-rotation.mdx
new file mode 100644
index 0000000000..a0864b656c
--- /dev/null
+++ b/docs/snippets/app-connections/databricks/configure-service-principal-for-rotation.mdx
@@ -0,0 +1,42 @@
+<Steps>
+ <Step title="Open workspace settings" titleSize="h3">
+ In Databricks, open the dropdown in the top right and select **Settings**.
+
+ ![Workspace Settings Page](/images/app-connections/databricks/workspace-settings.png)
+ </Step>
+ <Step title="Open service principals" titleSize="h3">
+ Under **Identity & Access**, select **Manage** in the **Service Principals** section.
+
+ ![Manage Service Principals](/images/app-connections/databricks/manage-service-principals.png)
+ </Step>
+ <Step title="Add a service principal" titleSize="h3">
+ Select **Add Service Principal**, then **Add New**, and create a service principal for Infisical.
+
+ ![Add Service Principal](/images/app-connections/databricks/add-service-principal.png)
+ ![Create Service Principal](/images/app-connections/databricks/create-service-principal.png)
+ </Step>
+ <Step title="Generate a secret" titleSize="h3">
+ Open the new service principal, select the **Secrets** tab, and select **Generate Secret**. Save the **Client ID** and **Secret** for the Infisical form.
+
+ ![Generate Secret](/images/app-connections/databricks/service-principal-secrets.png)
+ ![Copy IDs](/images/app-connections/databricks/service-principal-ids.png)
+ </Step>
+ <Step title="Grant rotation permissions" titleSize="h3">
+ The Infisical service principal needs to manage the secrets of every service principal whose secrets you want to rotate.
+
+ 1. Navigate to **Settings > Identity & Access > Groups** and select the admin group (typically named `admins` or `workspace-admins`). Select **Add** and pick the Infisical service principal.
+
+ ![Admin Group](/images/app-connections/databricks/admin-group.png)
+ ![Add to Admin Group](/images/app-connections/databricks/add-to-admin-group.png)
+ ![Add to Admin Group Modal](/images/app-connections/databricks/add-to-admin-group-form.png)
+
+ 2. For every service principal whose secrets you want to rotate, open **Settings > Identity & Access > Service Principals**, select the target, open its **Permissions** tab, and select **Grant access**.
+
+ ![Select Target Service Principal](/images/app-connections/databricks/select-target-service-principal.png)
+ ![Permissions Tab](/images/app-connections/databricks/permissions-tab.png)
+
+ 3. In **User, Group or Service Principal**, select the Infisical service principal. In **Permission**, select **Manage**. Select **Save**. Repeat for every target.
+
+ ![Assign Manage Permission](/images/app-connections/databricks/assign-manage-permission.png)
+ </Step>
+</Steps>
diff --git a/docs/snippets/app-connections/databricks/configure-service-principal.mdx b/docs/snippets/app-connections/databricks/configure-service-principal.mdx
new file mode 100644
index 0000000000..24b9950948
--- /dev/null
+++ b/docs/snippets/app-connections/databricks/configure-service-principal.mdx
@@ -0,0 +1,24 @@
+<Steps>
+ <Step title="Open workspace settings" titleSize="h3">
+ In Databricks, open the dropdown in the top right and select **Settings**.
+
+ ![Workspace Settings Page](/images/app-connections/databricks/workspace-settings.png)
+ </Step>
+ <Step title="Open service principals" titleSize="h3">
+ Under **Identity & Access**, select **Manage** in the **Service Principals** section.
+
+ ![Manage Service Principals](/images/app-connections/databricks/manage-service-principals.png)
+ </Step>
+ <Step title="Add a service principal" titleSize="h3">
+ Select **Add Service Principal**, then **Add New**, and create a service principal for Infisical.
+
+ ![Add Service Principal](/images/app-connections/databricks/add-service-principal.png)
+ ![Create Service Principal](/images/app-connections/databricks/create-service-principal.png)
+ </Step>
+ <Step title="Generate a secret" titleSize="h3">
+ Open the new service principal, select the **Secrets** tab, and select **Generate Secret**. Save the **Client ID** and **Secret** for the Infisical form.
+
+ ![Generate Secret](/images/app-connections/databricks/service-principal-secrets.png)
+ ![Copy IDs](/images/app-connections/databricks/service-principal-ids.png)
+ </Step>
+</Steps>
diff --git a/docs/snippets/app-connections/databricks/form-fields.mdx b/docs/snippets/app-connections/databricks/form-fields.mdx
new file mode 100644
index 0000000000..7740f7e1e0
--- /dev/null
+++ b/docs/snippets/app-connections/databricks/form-fields.mdx
@@ -0,0 +1,5 @@
+- **Name**: A descriptive name for the connection.
+- **Description** (optional): A note for future reference.
+- **Workspace URL**: The URL of your Databricks workspace.
+- **Client ID**: The Client ID of the Databricks service principal created for Infisical.
+- **Client Secret**: The [secret generated](#generate-a-secret) for that service principal.