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
docs(link-rot): fix broken links (#8974)
Adrian Kahalif4e9ac462eaa
diff --git a/docs/api-reference/endpoints/app-connections/fireworks/available.mdx b/docs/api-reference/endpoints/app-connections/fireworks/available.mdxnew file mode 100644index 0000000000..ed861d3695--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/available.mdx@@ -0,0 +1,4 @@+---+title: "Available"+openapi: "GET /api/v1/app-connections/fireworks/available"+---diff --git a/docs/api-reference/endpoints/app-connections/fireworks/create.mdx b/docs/api-reference/endpoints/app-connections/fireworks/create.mdxnew file mode 100644index 0000000000..1a3842a9a6--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/create.mdx@@ -0,0 +1,10 @@+---+title: "Create"+openapi: "POST /api/v1/app-connections/fireworks"+---++<Note>+ Check out the configuration docs for [Fireworks+ Connections](/integrations/app-connections/fireworks) to learn how to obtain the+ required credentials.+</Note>diff --git a/docs/api-reference/endpoints/app-connections/fireworks/delete.mdx b/docs/api-reference/endpoints/app-connections/fireworks/delete.mdxnew file mode 100644index 0000000000..b542614e2f--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/delete.mdx@@ -0,0 +1,4 @@+---+title: "Delete"+openapi: "DELETE /api/v1/app-connections/fireworks/{connectionId}"+---diff --git a/docs/api-reference/endpoints/app-connections/fireworks/get-by-id.mdx b/docs/api-reference/endpoints/app-connections/fireworks/get-by-id.mdxnew file mode 100644index 0000000000..b05906c958--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/get-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get by ID"+openapi: "GET /api/v1/app-connections/fireworks/{connectionId}"+---diff --git a/docs/api-reference/endpoints/app-connections/fireworks/get-by-name.mdx b/docs/api-reference/endpoints/app-connections/fireworks/get-by-name.mdxnew file mode 100644index 0000000000..ad446cc91b--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/get-by-name.mdx@@ -0,0 +1,4 @@+---+title: "Get by name"+openapi: "GET /api/v1/app-connections/fireworks/connection-name/{connectionName}"+---diff --git a/docs/api-reference/endpoints/app-connections/fireworks/list.mdx b/docs/api-reference/endpoints/app-connections/fireworks/list.mdxnew file mode 100644index 0000000000..8ec0c95f4e--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/list.mdx@@ -0,0 +1,4 @@+---+title: "List"+openapi: "GET /api/v1/app-connections/fireworks"+---diff --git a/docs/api-reference/endpoints/app-connections/fireworks/update.mdx b/docs/api-reference/endpoints/app-connections/fireworks/update.mdxnew file mode 100644index 0000000000..35b3f7e815--- /dev/null+++ b/docs/api-reference/endpoints/app-connections/fireworks/update.mdx@@ -0,0 +1,10 @@+---+title: "Update"+openapi: "PATCH /api/v1/app-connections/fireworks/{connectionId}"+---++<Note>+ Check out the configuration docs for [Fireworks+ Connections](/integrations/app-connections/fireworks) to learn how to obtain the+ required credentials.+</Note>diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/delete.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/delete.mdxnew file mode 100644index 0000000000..08a2e1c316--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/delete.mdx@@ -0,0 +1,4 @@+---+title: "Delete"+openapi: "DELETE /api/v2/secret-rotations/fireworks-api-key/{rotationId}"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-id.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-id.mdxnew file mode 100644index 0000000000..7b66ec1c5e--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get by ID"+openapi: "GET /api/v2/secret-rotations/fireworks-api-key/{rotationId}"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-name.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-name.mdxnew file mode 100644index 0000000000..dc45b568fc--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-by-name.mdx@@ -0,0 +1,4 @@+---+title: "Get by name"+openapi: "GET /api/v2/secret-rotations/fireworks-api-key/rotation-name/{rotationName}"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-generated-credentials-by-id.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-generated-credentials-by-id.mdxnew file mode 100644index 0000000000..bbdc2ad50d--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/get-generated-credentials-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get credentials by ID"+openapi: "GET /api/v2/secret-rotations/fireworks-api-key/{rotationId}/generated-credentials"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/list.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/list.mdxnew file mode 100644index 0000000000..65f7c5a349--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/list.mdx@@ -0,0 +1,4 @@+---+title: "List"+openapi: "GET /api/v2/secret-rotations/fireworks-api-key"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/rotate-secrets.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/rotate-secrets.mdxnew file mode 100644index 0000000000..6432c62eb0--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/rotate-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Rotate secrets"+openapi: "POST /api/v2/secret-rotations/fireworks-api-key/{rotationId}/rotate-secrets"+---diff --git a/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/update.mdx b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/update.mdxnew file mode 100644index 0000000000..74d7313e36--- /dev/null+++ b/docs/api-reference/endpoints/secret-rotations/fireworks-api-key/update.mdx@@ -0,0 +1,9 @@+---+title: "Update"+openapi: "PATCH /api/v2/secret-rotations/fireworks-api-key/{rotationId}"+---++<Note>+ Check out the configuration docs for [Fireworks API Key Rotations](/documentation/platform/secret-rotation/fireworks-api-key) to learn how to obtain the+ required parameters.+</Note>\ No newline at end of filediff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/delete.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/delete.mdxnew file mode 100644index 0000000000..d6e1e3f37f--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/delete.mdx@@ -0,0 +1,4 @@+---+title: "Delete"+openapi: "DELETE /api/v1/secret-syncs/spacelift/{syncId}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-id.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-id.mdxnew file mode 100644index 0000000000..12b0ec5601--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-id.mdx@@ -0,0 +1,4 @@+---+title: "Get by ID"+openapi: "GET /api/v1/secret-syncs/spacelift/{syncId}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-name.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-name.mdxnew file mode 100644index 0000000000..471882dabb--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/get-by-name.mdx@@ -0,0 +1,4 @@+---+title: "Get by name"+openapi: "GET /api/v1/secret-syncs/spacelift/sync-name/{syncName}"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/list.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/list.mdxnew file mode 100644index 0000000000..0de5562751--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/list.mdx@@ -0,0 +1,4 @@+---+title: "List"+openapi: "GET /api/v1/secret-syncs/spacelift"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/remove-secrets.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/remove-secrets.mdxnew file mode 100644index 0000000000..981d8414d2--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/remove-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Remove secrets"+openapi: "POST /api/v1/secret-syncs/spacelift/{syncId}/remove-secrets"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/sync-secrets.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/sync-secrets.mdxnew file mode 100644index 0000000000..732a4388de--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/sync-secrets.mdx@@ -0,0 +1,4 @@+---+title: "Sync secrets"+openapi: "POST /api/v1/secret-syncs/spacelift/{syncId}/sync-secrets"+---diff --git a/docs/api-reference/endpoints/secret-syncs/spacelift/update.mdx b/docs/api-reference/endpoints/secret-syncs/spacelift/update.mdxnew file mode 100644index 0000000000..29fad493ce--- /dev/null+++ b/docs/api-reference/endpoints/secret-syncs/spacelift/update.mdx@@ -0,0 +1,4 @@+---+title: "Update"+openapi: "PATCH /api/v1/secret-syncs/spacelift/{syncId}"+---diff --git a/docs/cli/reference.mdx b/docs/cli/reference.mdxindex 8afee1685c..4685301e18 100644--- a/docs/cli/reference.mdx+++ b/docs/cli/reference.mdx@@ -1325,7 +1325,7 @@ For an agent on your own computer, [infisical sm agent-proxy run](/cli/referenceLaunch an agent that sends its requests through an agent proxy on another host, started with [infisical sm agent-proxy start](/cli/reference#sm-agent-proxy-start). See [Standalone Agent Proxy](/documentation/platform/agent-proxy/standalone-agent-proxy).-The command authenticates as the agent's machine identity, with `--client-id` and `--client-secret` or a token. It doesn't use your login. It then starts the agent with `HTTP_PROXY` and `HTTPS_PROXY` set to the proxy's address, and sets the variables that make the agent's HTTP clients trust your organization's root certificate. See [what `connect` puts in the agent's environment](/documentation/platform/agent-proxy/standalone-agent-proxy#what-connect-puts-in-the-agents-environment).+The command authenticates as the agent's machine identity, with `--client-id` and `--client-secret` or a token. It doesn't use your login. It then starts the agent with `HTTP_PROXY` and `HTTPS_PROXY` set to the proxy's address, and sets the variables that make the agent's HTTP clients trust your organization's root certificate. See [what `connect` puts in the agent's environment](/documentation/platform/agent-proxy/standalone-agent-proxy#what-connect-puts-in-the-agent’s-environment).If the agent can read a secret or lease a dynamic secret that a proxied service brokers to it, the command refuses to start, because the agent would get the real value and bypass the proxy.diff --git a/docs/docs.json b/docs/docs.jsonindex 1d90905122..88bba8c804 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -1513,7 +1513,6 @@"api-reference/endpoints/projects/get-project","api-reference/endpoints/projects/list-projects","api-reference/endpoints/projects/update-project",- "api-reference/endpoints/projects/secret-snapshots",{"group": "Legacy","pages": [@@ -3379,9 +3378,7 @@"api-reference/endpoints/secret-syncs/azure-entra-id-scim/create","api-reference/endpoints/secret-syncs/azure-entra-id-scim/update","api-reference/endpoints/secret-syncs/azure-entra-id-scim/delete",- "api-reference/endpoints/secret-syncs/azure-entra-id-scim/sync-secrets",- "api-reference/endpoints/secret-syncs/azure-entra-id-scim/import-secrets",- "api-reference/endpoints/secret-syncs/azure-entra-id-scim/remove-secrets"+ "api-reference/endpoints/secret-syncs/azure-entra-id-scim/sync-secrets"]},{diff --git a/docs/documentation/platform/agent-vault/guides/custom-agent.mdx b/docs/documentation/platform/agent-vault/guides/custom-agent.mdxindex 16692ce12a..200719a366 100644--- a/docs/documentation/platform/agent-vault/guides/custom-agent.mdx+++ b/docs/documentation/platform/agent-vault/guides/custom-agent.mdx@@ -104,7 +104,7 @@ openssl x509 -in ca.pem -noout -fingerprint -sha256Compare the colon-separated value with the proxy's fingerprint on the **Proxies** page in Agent Vault. The **Certificate Authority** column shows the start of the fingerprint, and hovering over it shows the full value. If the values don't match, don't use the file.-Store `ca.pem` where the agent can read it. The certificate isn't secret, so you can add it to the agent's container image. If you [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxys-token), download the certificate again.+Store `ca.pem` where the agent can read it. The certificate isn't secret, so you can add it to the agent's container image. If you [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxy’s-token), download the certificate again.## Step 3: Replace the API keys with placeholdersdiff --git a/docs/documentation/platform/agent-vault/guides/modal.mdx b/docs/documentation/platform/agent-vault/guides/modal.mdxindex f6171ae62c..4c7ac96471 100644--- a/docs/documentation/platform/agent-vault/guides/modal.mdx+++ b/docs/documentation/platform/agent-vault/guides/modal.mdx@@ -707,7 +707,7 @@ Claude Code replies, even though its sandbox has no Anthropic API key and can'tEach run now gets its own sandbox, proxy, and session. The only credential in the agent's container is a session token, and your code revokes the session when the run ends.</Check>-To check which requests the agent made, [set up session logs](/documentation/platform/agent-vault/session-logs#setting-up-session-logs), then [view the session's logs](/documentation/platform/agent-vault/sessions#view-session-logs) in Agent Vault. Requests that got a credential have the outcome **Brokered**.+To check which requests the agent made, [set up session logs](/documentation/platform/agent-vault/session-logs), then [view the session's logs](/documentation/platform/agent-vault/sessions#view-session-logs) in Agent Vault. Requests that got a credential have the outcome **Brokered**.## Security considerations@@ -720,7 +720,7 @@ The agent's container can't connect to the internet directly, but it has two kin### Compromised sandboxes-Each sidecar has a copy of the proxy token. If you think someone took control of a sandbox, [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxys-token), then put the new token in the `agent-vault-proxy` secret in Modal.+Each sidecar has a copy of the proxy token. If you think someone took control of a sandbox, [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxy’s-token), then put the new token in the `agent-vault-proxy` secret in Modal.## Troubleshootingdiff --git a/docs/documentation/platform/agent-vault/proxies.mdx b/docs/documentation/platform/agent-vault/proxies.mdxindex c87816e445..7da9e934c6 100644--- a/docs/documentation/platform/agent-vault/proxies.mdx+++ b/docs/documentation/platform/agent-vault/proxies.mdx@@ -320,7 +320,7 @@ Both actions are on the proxy's menu:| Action | What happens ||--------|--------------|-| **Revoke Access** | The proxy will stop adding credentials to requests. To bring it back, [rotate its token](#rotate-a-proxys-token) |+| **Revoke Access** | The proxy will stop adding credentials to requests. To bring it back, [rotate its token](#rotate-a-proxy’s-token) || **Delete** | Infisical removes the proxy, and the proxy will stop adding credentials to requests. You can't undo this |Revoke access if you think a machine running the proxy is compromised.diff --git a/docs/documentation/platform/agent-vault/sessions-cli.mdx b/docs/documentation/platform/agent-vault/sessions-cli.mdxindex 5557719315..4361af6cc9 100644--- a/docs/documentation/platform/agent-vault/sessions-cli.mdx+++ b/docs/documentation/platform/agent-vault/sessions-cli.mdx@@ -65,7 +65,7 @@ The CLI downloads the proxy's certificate at the start of each run. If the agentinfisical agent-vault run --access-bundle <access-bundle-name> --ttl 2h --ca-fingerprint <fingerprint> -- <agent-command>```-Copy the fingerprint from the **Certificate Authority** column on the **Proxies** page. If you [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxys-token), update the fingerprint.+Copy the fingerprint from the **Certificate Authority** column on the **Proxies** page. If you [rotate the proxy's token](/documentation/platform/agent-vault/proxies#rotate-a-proxy’s-token), update the fingerprint.## Step 3: Run the agent automaticallydiff --git a/docs/documentation/platform/pam/auditing.mdx b/docs/documentation/platform/pam/auditing.mdxindex f6531406cb..8e17bffd75 100644--- a/docs/documentation/platform/pam/auditing.mdx+++ b/docs/documentation/platform/pam/auditing.mdx@@ -21,7 +21,7 @@ Go to **Privileged Access Management** > **Audit Logs**. The audit log shows theEach event names the actor, the action, and the folder or account it affected, along with when it happened. If the actor was a [machine identity](/documentation/platform/identities/machine-identities), the event shows **Machine Identity** in place of an email address. When an [AI agent](/documentation/platform/pam/ai-agents/overview) connects to an account, Infisical records the event under the user or machine identity that started the agent.-To filter events by date, event type, or actor, check out [Filtering audit logs](/documentation/platform/audit-logs#filtering-audit-logs). For filters that answer common PAM questions, such as who accessed an account, check out [Common filters](/documentation/platform/audit-logs#privileged-access-manager).+To filter events by date, event type, or actor, check out [Filtering audit logs](/documentation/platform/audit-logs#filtering-audit-logs). For filters that answer common PAM questions, such as who accessed an account, check out [Common filters](/documentation/platform/audit-logs#privileged-access-management-pam).## What gets loggeddiff --git a/docs/documentation/platform/pam/sessions/external-storage.mdx b/docs/documentation/platform/pam/sessions/external-storage.mdxindex 3a1f5b742d..ef9c508f6c 100644--- a/docs/documentation/platform/pam/sessions/external-storage.mdx+++ b/docs/documentation/platform/pam/sessions/external-storage.mdx@@ -123,7 +123,7 @@ If Infisical can't reach the bucket, the template isn't saved and the error mess### Use a different bucket for one account-To store a Windows or Windows AD account's recordings in a different bucket from its template, [open the account's settings](/documentation/platform/pam/accounts/manage#open-an-accounts-settings), go to the **Advanced** tab, and select **Override** under **Recording Settings**.+To store a Windows or Windows AD account's recordings in a different bucket from its template, [open the account's settings](/documentation/platform/pam/accounts/manage#open-an-account’s-settings), go to the **Advanced** tab, and select **Override** under **Recording Settings**.The override only changes the bucket details, so the template's **Storage backend** must still be **S3 Bucket**. Other account types always use their template's storage.diff --git a/docs/documentation/platform/pam/templates/overview.mdx b/docs/documentation/platform/pam/templates/overview.mdxindex 69fab88c21..cead1fe610 100644--- a/docs/documentation/platform/pam/templates/overview.mdx+++ b/docs/documentation/platform/pam/templates/overview.mdx@@ -62,7 +62,7 @@ Machine identities and [AI agents](/documentation/platform/pam/ai-agents/overvie| **Session Log Masking** | Hides text that matches these patterns in session recordings |<Note>-You can [override the gateway](/documentation/platform/pam/accounts/manage#override-the-templates-settings) for one account on the account's **Advanced** tab. For Windows and Windows AD accounts, you can also override the recording bucket there.+You can [override the gateway](/documentation/platform/pam/accounts/manage#override-the-template’s-settings) for one account on the account's **Advanced** tab. For Windows and Windows AD accounts, you can also override the recording bucket there.</Note>The **General** tab also has settings for [credential rotation](/documentation/platform/pam/credential-rotation/overview) and [credential health](/documentation/platform/pam/credential-health/overview) checks, for account types that support them.diff --git a/docs/documentation/platform/pit-recovery.mdx b/docs/documentation/platform/pit-recovery.mdxindex 255824892a..ceced73516 100644--- a/docs/documentation/platform/pit-recovery.mdx+++ b/docs/documentation/platform/pit-recovery.mdx@@ -10,7 +10,7 @@ description: "Learn how to rollback secrets and configurations to any snapshot wto use it.</Info>-Infisical's point-in-time recovery functionality allows secrets to be rolled back to any point in time for any given [folder](./folder) or [environment](/documentation/platform/project#project-environments).+Infisical's point-in-time recovery functionality allows secrets to be rolled back to any point in time for any given [folder](./folder) or [environment](/documentation/platform/secrets-mgmt/project#project-environments).The short video below walks through secret versioning and point-in-time recovery, covering how Infisical keeps a history of every secret change and how to roll back to a previous state.diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager.mdxindex d5c4290b71..f6b30e71f5 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager.mdx@@ -166,7 +166,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Elastic Load Balancer" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer">Deploy certificates directly to ALB/NLB listeners.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer.mdxindex 82407dc4cd..918e4e6e05 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer.mdx@@ -198,7 +198,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for other AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager.mdxindex e2e2a4646c..eaff67a1aa 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager.mdx@@ -242,7 +242,7 @@ AWS Secrets Manager has specific naming requirements for secrets:<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/azure-key-vault.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/azure-key-vault.mdxindex 4069bdd82f..1d06d8bdca 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/azure-key-vault.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/azure-key-vault.mdx@@ -164,7 +164,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/chef.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/chef.mdxindex a47e99e88a..729f340135 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/chef.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/chef.mdx@@ -228,7 +228,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate.mdxindex d8e70f4b6c..903986b8c3 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate.mdx@@ -149,7 +149,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/f5-big-ip.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/f5-big-ip.mdxindex b2a90351f7..e191ee94a7 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/f5-big-ip.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/f5-big-ip.mdx@@ -192,7 +192,7 @@ To manually sync, use the [Sync Certificates](/api-reference/endpoints/pki/syncs<Card title="NetScaler" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/netscaler">Deploy certificates to Citrix NetScaler ADC appliances.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager.mdxindex cc4b6f2784..f9545de312 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager.mdx@@ -276,7 +276,7 @@ Use the [Sync Certificates](/api-reference/endpoints/pki/syncs/gcp-certificate-m<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for use with AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster.mdxindex 8a4d14c6a8..e773bfe3e4 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster.mdx@@ -176,7 +176,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="NetScaler" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/netscaler">Deploy certificates to Citrix NetScaler appliances.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/netscaler.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/netscaler.mdxindex 6c6e6e042b..9a02af3661 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/netscaler.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/netscaler.mdx@@ -178,7 +178,7 @@ To manually sync certificates, use the [Sync Certificates](/api-reference/endpoi<Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">Import certificates into ACM for AWS services.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central.mdxindex 3b8879c84e..f31ec7eb5a 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central.mdx@@ -171,7 +171,7 @@ When a certificate is renewed in Infisical, the renewed certificate is automatic<Card title="NetScaler" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/netscaler">Deploy certificates to Citrix NetScaler ADC appliances.</Card>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#server-driven-renewal">+ <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificates#renewal">Enable automatic certificate renewal and syncing.</Card><Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">diff --git a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdxindex 532b4cd882..f9a37eee8f 100644--- a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx+++ b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx@@ -140,7 +140,7 @@ Throughout this guide, replace `<namespace>` with the namespace where your workl</Tabs></Step>- <Step title="Create the Infisical Issuer">+ <Step title="Create the Infisical Issuer" id="create-the-infisical-issuer">Create an `Issuer` (or `ClusterIssuer`) referencing your Application and Profile by name, and the credentials Secret from the previous step.<Tabs>diff --git a/docs/documentation/platform/scim/group-mappings.mdx b/docs/documentation/platform/scim/group-mappings.mdxindex fce3a3d132..9911cbe6e1 100644--- a/docs/documentation/platform/scim/group-mappings.mdx+++ b/docs/documentation/platform/scim/group-mappings.mdx@@ -12,7 +12,7 @@ description: "Learn how to enhance your SCIM implementation using group mappings## SCIM group to organization role mapping-By default, when users are provisioned via SCIM, they will be assigned the default organization role configured in [Organization General Settings](/documentation/platform/organization#settings).+By default, when users are provisioned via SCIM, they will be assigned the default organization role configured in [Organization General Settings](/documentation/platform/organization#organization-settings).For more precise control over membership roles, you can set up SCIM Group to Organization Role Mappings. This enables you to assign specific roles based on the group from which a user is provisioned.diff --git a/docs/documentation/platform/secret-rotation/auth0-client-secret.mdx b/docs/documentation/platform/secret-rotation/auth0-client-secret.mdxindex 9fdccb5467..4032cdb0fd 100644--- a/docs/documentation/platform/secret-rotation/auth0-client-secret.mdx+++ b/docs/documentation/platform/secret-rotation/auth0-client-secret.mdx@@ -5,7 +5,7 @@ description: "Learn how to automatically rotate Auth0 Client Secrets."---<Note>- **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase-rotation)**+ **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase)**This rotation updates a single credential set in place. Old credentials become invalid immediately upon rotation. This means that clients using the previous credentials will fail to authenticate until they retrieve the new credentials.diff --git a/docs/documentation/platform/secret-rotation/convex-access-key.mdx b/docs/documentation/platform/secret-rotation/convex-access-key.mdxindex be20f44e13..7ff32c51e4 100644--- a/docs/documentation/platform/secret-rotation/convex-access-key.mdx+++ b/docs/documentation/platform/secret-rotation/convex-access-key.mdx@@ -5,7 +5,7 @@ description: "Learn how to automatically rotate Convex access keys."---<Note>- **Rotation Type: [Dual-Phase](/documentation/platform/secret-rotation/overview#dual-phase-rotation)**+ **Rotation Type: [Dual-Phase](/documentation/platform/secret-rotation/overview#dual-phase)**This rotation maintains two active credential sets with overlapping validity, ensuring zero-downtime during rotation cycles.</Note>diff --git a/docs/documentation/platform/secret-rotation/ldap-password.mdx b/docs/documentation/platform/secret-rotation/ldap-password.mdxindex cd23e0d3a3..14c4a36c50 100644--- a/docs/documentation/platform/secret-rotation/ldap-password.mdx+++ b/docs/documentation/platform/secret-rotation/ldap-password.mdx@@ -5,7 +5,7 @@ description: "Learn how to automatically rotate LDAP passwords."---<Note>- **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase-rotation)**+ **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase)**This rotation updates a single credential set in place. Old credentials become invalid immediately upon rotation. This means that clients using the previous credentials will fail to authenticate until they retrieve the new credentials.diff --git a/docs/documentation/platform/secret-rotation/unix-linux-local-account.mdx b/docs/documentation/platform/secret-rotation/unix-linux-local-account.mdxindex b91e1e259e..d12e46c4f6 100644--- a/docs/documentation/platform/secret-rotation/unix-linux-local-account.mdx+++ b/docs/documentation/platform/secret-rotation/unix-linux-local-account.mdx@@ -5,7 +5,7 @@ description: "Learn how to automatically rotate Unix/Linux local account passwor---<Note>- **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase-rotation)**+ **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase)**This rotation updates a single credential set in place. Old credentials become invalid immediately upon rotation. This means that clients using the previous credentials will fail to authenticate until they retrieve the new credentials.diff --git a/docs/documentation/platform/secret-rotation/windows-local-account.mdx b/docs/documentation/platform/secret-rotation/windows-local-account.mdxindex 589a69cba0..86f20a337d 100644--- a/docs/documentation/platform/secret-rotation/windows-local-account.mdx+++ b/docs/documentation/platform/secret-rotation/windows-local-account.mdx@@ -5,7 +5,7 @@ description: "Learn how to automatically rotate Windows local account passwords---<Note>- **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase-rotation)**+ **Rotation Type: [Single-Phase](/documentation/platform/secret-rotation/overview#single-phase)**This rotation updates a single credential set in place. Old credentials become invalid immediately upon rotation. This means that clients using the previous credentials will fail to authenticate until they retrieve the new credentials.diff --git a/docs/integrations/platforms/docker.mdx b/docs/integrations/platforms/docker.mdxindex b9e292c1a8..6d131eaf5e 100644--- a/docs/integrations/platforms/docker.mdx+++ b/docs/integrations/platforms/docker.mdx@@ -4,7 +4,7 @@ sidebarTitle: "Docker"description: "Store secrets in Infisical and deliver them to a Dockerized application at runtime."----This guide walks you through injecting secrets from Infisical into a Dockerized application as environment variables. You can [fetch secrets when the container starts](#fetch-at-startup) or [export them from the host](#pass-with-docker-run) when you run the container.+This guide walks you through injecting secrets from Infisical into a Dockerized application as environment variables. You can [fetch secrets when the container starts](#fetch-at-startup-recommended) or [export them from the host](#docker-run-interactive) when you run the container.<Tip>Visual learner? Watch an [overview of managing secrets in Docker with Infisical](https://www.youtube.com/watch?v=oU2nNBwlOTA).@@ -292,7 +292,7 @@ Choose how Docker should receive your application secrets:## Use with Docker Compose-If you [fetch secrets at startup](#fetch-at-startup), you can use [Docker Compose](https://docs.docker.com/compose/) to build and run one or more configured service images.+If you [fetch secrets at startup](#fetch-at-startup-recommended), you can use [Docker Compose](https://docs.docker.com/compose/) to build and run one or more configured service images.[Configure each image](/integrations/platforms/docker#step-4-update-your-dockerfile) to start through `infisical sm run`, then configure your Compose file for your Infisical deployment:diff --git a/docs/integrations/secret-syncs/spacelift.mdx b/docs/integrations/secret-syncs/spacelift.mdxindex bc7df4fbba..e2304dfd4f 100644--- a/docs/integrations/secret-syncs/spacelift.mdx+++ b/docs/integrations/secret-syncs/spacelift.mdx@@ -66,7 +66,7 @@ Infisical's Spacelift Sync pushes secrets from Infisical into a Spacelift contex- **File Path**: The path for the mounted `.env` file relative to `/mnt/workspace/` (e.g., `secrets.env`). Required.<Warning>- Every sync replaces the entire file with the secrets from Infisical. This means that if there any entries in the same path that came from outside Infisical, those entires will be lost on the next sync. Since neither setting a key schema or **Disable secret deletion** in [sync options](#Sync-Options) prevents this, we recommend pointing **File Path** at a file that only this sync writes to.+ Every sync replaces the entire file with the secrets from Infisical. This means that if there any entries in the same path that came from outside Infisical, those entires will be lost on the next sync. Since neither setting a key schema or **Disable secret deletion** in [sync options](#sync-options) prevents this, we recommend pointing **File Path** at a file that only this sync writes to.</Warning>diff --git a/docs/self-hosting/faq.mdx b/docs/self-hosting/faq.mdxindex 67b5757b98..7ef7b0b954 100644--- a/docs/self-hosting/faq.mdx+++ b/docs/self-hosting/faq.mdx@@ -17,6 +17,6 @@ However, in the event you choose to use Infisical without SSL, you can do so by</Accordion><Accordion title="How can I upgrade my Infisical instance to Postgres version?">- Follow the step by step guide [here](self-hosting/guides/mongo-to-postgres) to learn how.+ Follow the step by step guide [here](/self-hosting/guides/mongo-to-postgres) to learn how.</Accordion>diff --git a/docs/self-hosting/guides/automated-bootstrapping.mdx b/docs/self-hosting/guides/automated-bootstrapping.mdxindex da13eedc73..d3887d8652 100644--- a/docs/self-hosting/guides/automated-bootstrapping.mdx+++ b/docs/self-hosting/guides/automated-bootstrapping.mdx@@ -117,7 +117,7 @@ You can bootstrap an Infisical instance using the API, CLI, or Helm chart.```</Tab><Tab title="Helm Chart">- When deploying Infisical using the official [Helm chart](/self-hosting/deployment-options/kubernetes-helm#kubernetes-via-helm-chart), you can enable automatic bootstrapping that runs as part of the deployment process. This eliminates the need to manually bootstrap the instance after deployment.+ When deploying Infisical using the official [Helm chart](/self-hosting/deployment-options/kubernetes-helm), you can enable automatic bootstrapping that runs as part of the deployment process. This eliminates the need to manually bootstrap the instance after deployment.The bootstrapping process automatically generates a Kubernetes secret containing the instance admin token, which can then be referenced by Crossplane providers, Terraform operators, or other automation systems for further infrastructure provisioning and configuration.diff --git a/docs/snippets/documentation/platform/pki/guides/request-cert-setup.mdx b/docs/snippets/documentation/platform/pki/guides/request-cert-setup.mdxindex dd0629e173..235b18ff56 100644--- a/docs/snippets/documentation/platform/pki/guides/request-cert-setup.mdx+++ b/docs/snippets/documentation/platform/pki/guides/request-cert-setup.mdx@@ -8,7 +8,7 @@The CA you configure will be used to issue the certificate back to your client; it can be either Internal or External:- [Internal CA](/documentation/platform/pki/ca/private-ca): If you're building your own PKI and wish to issue certificates for internal use, you should- follow the guide [here](/documentation/platform/pki/ca/private-ca#guide-to-creating-a-ca-hierarchy) to create at minimum a root CA and an intermediate/issuing CA+ follow the guide [here](/documentation/platform/pki/ca/private-ca#create-a-ca-hierarchy) to create at minimum a root CA and an intermediate/issuing CAwithin Infisical.- [External CA](/documentation/platform/pki/ca/external-ca): If you have existing PKI infrastructure or wish to connect to a public CA (e.g. [Let's Encrypt](/documentation/platform/pki/ca/lets-encrypt), [DigiCert](/documentation/platform/pki/ca/digicert), etc.) to issue TLS certificates,