docs: security hardening for untrusted multitenancy deployments (#14061)

* docs: workflow api schema breaking change

* docs: docker image defaults changes for security

* docs: untrusted multitenant settings

* docs: lessen code font padding

* docs: fix traces link

* docs: identify typo

* docs: peer review

Author: mendonk

docker_example/README.md

@@ -1,6 +1,6 @@
-# Running LangFlow with Docker
+# Run Langflow with Docker
 
-This guide will help you get LangFlow up and running using Docker and Docker Compose.
+This guide will help you get Langflow up and running using Docker and Docker Compose.
 
 ## Prerequisites
 
@@ -9,7 +9,7 @@ This guide will help you get LangFlow up and running using Docker and Docker Com
 
 ## Steps
 
-1. Clone the LangFlow repository:
+1. Clone the Langflow repository:
 
    ```sh
    git clone https://github.com/langflow-ai/langflow.git
@@ -21,12 +21,13 @@ This guide will help you get LangFlow up and running using Docker and Docker Com
    cd langflow/docker_example
    ```
 
-3. Create a `.env` file with the LangFlow admin password:
+3. Create a `.env` file with the Langflow admin password set:
 
    ```sh
-   LANGFLOW_SUPERUSER_PASSWORD=replace-with-a-strong-password
+   LANGFLOW_SUPERUSER_PASSWORD=SUPERUSER_PASSWORD
    ```
 
+   Replace `SUPERUSER_PASSWORD` with a strong password for the Langflow superuser.
    The default admin username is `langflow`.
 
 4. Run the Docker Compose file:
@@ -35,27 +36,27 @@ This guide will help you get LangFlow up and running using Docker and Docker Com
    docker compose up
    ```
 
-LangFlow will now be accessible at [http://localhost:7860/](http://localhost:7860/).
+Langflow will now be accessible at [http://localhost:7860/](http://localhost:7860/).
 
-## Docker Compose Configuration
+## Configure Docker Compose
 
 The Docker Compose configuration spins up two services: `langflow` and `postgres`.
 
-### LangFlow Service
+### Langflow service
 
 The `langflow` service uses the `langflowai/langflow:latest` Docker image and exposes port 7860. It depends on the `postgres` service.
 
 Environment variables:
 
 - `LANGFLOW_DATABASE_URL`: The connection string for the PostgreSQL database.
 - `LANGFLOW_SUPERUSER_PASSWORD`: The initial admin password. This value is required in `.env`.
-- `LANGFLOW_CONFIG_DIR`: The directory where LangFlow stores logs, file storage, monitor data, and secret keys.
+- `LANGFLOW_CONFIG_DIR`: The directory where Langflow stores logs, file storage, monitor data, and secret keys.
 
 Volumes:
 
 - `langflow-data`: This volume is mapped to `/app/langflow` in the container.
 
-### PostgreSQL Service
+### PostgreSQL service
 
 The `postgres` service uses the `postgres:16-trixie` Docker image and exposes port 5432. The image is pinned to a specific Debian base (`trixie`, Debian 13) so the `postgres:16` tag cannot silently roll its underlying OS, which would otherwise produce a glibc collation version mismatch warning on existing data volumes.
 
@@ -89,6 +90,6 @@ docker compose exec postgres \
 
 Fresh installs are unaffected.
 
-## Switching to a Specific LangFlow Version
+## Switching to a specific Langflow version
 
-If you want to use a specific version of LangFlow, you can modify the `image` field under the `langflow` service in the Docker Compose file. For example, to use version 1.0-alpha, change `langflowai/langflow:latest` to `langflowai/langflow:1.0-alpha`.
+If you want to use a specific version of Langflow, you can modify the `image` field under the `langflow` service in the Docker Compose file. For example, to use version 1.0-alpha, change `langflowai/langflow:latest` to `langflowai/langflow:1.0-alpha`.

docs/css/tokens.css

@@ -4,7 +4,7 @@
   --ifm-navbar-padding-vertical: 0;
   --ifm-global-radius: 10px;
   --ifm-code-border-radius: 4px;
-  --ifm-code-padding-horizontal: 0.4em;
+  --ifm-code-padding-horizontal: 0.2em;
   --ifm-navbar-item-padding-vertical: 0;
   --ifm-font-family-base: "Geist", Inter, -apple-system, BlinkMacSystemFont,
     Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI emoji";

docs/docs/Deployment/deployment-block-custom-components.mdx

@@ -15,7 +15,9 @@ LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false
 When set to `false`, Langflow blocks creating custom components and changing code in the visual editor.
 
 When unset or `true`, Langflow allows custom code.
-Existing Langflow installations will keep the default `true` behavior until you opt in to this restriction.
+Existing non-Docker installations keep the default `true` behavior until you opt in to this restriction.
+
+As of Langflow 1.11.x, official Langflow Docker images set `LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false` at image build time, along with related [component hardening](/api-keys-and-authentication#multi-tenant-component-hardening) flags.
 
 This environment variable is a beta feature, and should not be your only safeguard in production environments.
 

docs/docs/Deployment/deployment-docker.mdx

@@ -13,18 +13,25 @@ This guide demonstrates several ways to run Langflow with [Docker](https://docs.
 
 * [Quickstart](#quickstart): Start a Langflow container with default values.
 * [Use Docker Compose](#docker-compose): Run Langflow with a persistent PostgreSQL database and configurable environment variables.
-* [Customize the Docker image](#customize): Package a flow or add your own code into a custom image built on top of the official Langflow image.
+* [Customize the Docker Compose file](#customize): Package a flow or add your own code into a custom image built on top of the official Langflow image.
 * [Build and run the Docker image from source](#build-from-source): Build a Docker image from a local clone of the repo, or start a full development environment with hot reload on both frontend and backend.
 * [Upgrade the Langflow Docker image](#upgrade-the-langflow-docker-image): Upgrade to a newer image without losing your database or flows.
+* [Docker image security defaults](#docker-image-security-defaults): Hardened environment variables baked into published images, and how to override them for local use.
 
 ## Quickstart {#quickstart}
 
 With Docker installed and running on your system, run the following command:
 
 ```shell
-docker run -p 7860:7860 -e LANGFLOW_AUTO_LOGIN=true langflowai/langflow:latest
+docker run -p 7860:7860 \
+  -e LANGFLOW_AUTO_LOGIN=true \
+  -e LANGFLOW_SUPERUSER_PASSWORD=SUPERUSER_PASSWORD \
+  langflowai/langflow:latest
 ```
 
+Replace `SUPERUSER_PASSWORD` with a strong password for the Langflow superuser.
+As of Langflow 1.11.x, images include [security defaults](#docker-image-security-defaults) that you may need to override for local workflows.
+
 Then, access Langflow at `http://localhost:7860/`.
 
 This starts a pre-built Docker image with automatic login enabled for local development.
@@ -75,9 +82,11 @@ Configure a container's database credentials using a `.env` file.
     # Langflow configuration
     LANGFLOW_DATABASE_URL=postgresql://myuser:mypassword@postgres:5432/langflow
     LANGFLOW_CONFIG_DIR=/app/langflow
-    LANGFLOW_SUPERUSER_PASSWORD=replace-with-a-strong-password
+    LANGFLOW_SUPERUSER_PASSWORD=SUPERUSER_PASSWORD
     ```
 
+    Replace `SUPERUSER_PASSWORD` with a strong password for the Langflow superuser.
+
 2. Edit `docker-compose.yml` to replace the hardcoded values with variable references for both the `langflow` and `postgres` services:
 
     ```yaml
@@ -189,7 +198,6 @@ This example replaces the built-in **Message History** component, but the same p
     docker run -p 7860:7860 -e LANGFLOW_AUTO_LOGIN=true myuser/langflow-custom:1.0.0
     ```
 
-
 ## Build and run the Docker image from source {#build-from-source}
 
 :::tip
@@ -212,10 +220,17 @@ This builds `docker/build_and_push.Dockerfile` and tags the result `langflow:<ve
 To run the image after building, run:
 
 ```shell
-docker run -p 7860:7860 langflow:<version>
+docker run -p 7860:7860 \
+  -e LANGFLOW_SUPERUSER_PASSWORD=SUPERUSER_PASSWORD \
+  langflow:VERSION
 ```
 
-Replace `<version>` with the version in `pyproject.toml` at the repo root.
+Replace the following:
+
+* `SUPERUSER_PASSWORD`: a strong password for the Langflow superuser
+* `VERSION`: the version in `pyproject.toml` at the repo root
+
+The image sets `LANGFLOW_AUTO_LOGIN=false` and the [component hardening defaults](#docker-image-security-defaults), so a superuser password is required unless you set `LANGFLOW_AUTO_LOGIN=true`.
 
 To build only the LFX executor CLI image instead of the full Langflow application, run:
 
@@ -349,12 +364,50 @@ For example, this Docker Compose file uses a bind mount for Langflow data (`./la
     With `docker run`, use the same volume mount and the new image tag:
 
     ```bash
-    docker run -p 7860:7860 -v langflow-data:/app/langflow -e LANGFLOW_SUPERUSER_PASSWORD=replace-with-a-strong-password langflowai/langflow:1.11.0
+    docker run -p 7860:7860 \
+      -v langflow-data:/app/langflow \
+      -e LANGFLOW_SUPERUSER_PASSWORD=SUPERUSER_PASSWORD \
+      langflowai/langflow:1.11.0
     ```
 
+    Replace `SUPERUSER_PASSWORD` with a strong password for the Langflow superuser.
+
 This approach keeps the persistent volumes separate from the Langflow container, so you can upgrade the Langflow application without losing data.
 
 If you need to upgrade to a custom image based on a Langflow release, such as to add `uv` in `1.8.0`, first build a derived image from the official image, and then follow the same steps above.
 Set the custom image in your compose file or `docker run`, and then pull and restart.
 
 For a minimal Dockerfile that adds `uv` to the 1.8.0 image, see the [release notes](/release-notes) ("Docker image no longer includes uv or uvx").
+
+## Docker image security defaults {#docker-image-security-defaults}
+
+As of Langflow 1.11.x, official Langflow Docker images set `LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false` at image build time, and include stricter defaults for the following environment variables:
+
+| Variable | Image value | Application default (pip / local) |
+|----------|-------------|-----------------------------------|
+| `LANGFLOW_AUTO_LOGIN` | `false` | `true` |
+| `LANGFLOW_ALLOW_CUSTOM_COMPONENTS` | `false` | `true` |
+| `LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS` | `true` | `false` |
+| `LANGFLOW_RESTRICT_LOCAL_FILE_ACCESS` | `true` | `false` |
+| `LANGFLOW_MCP_SERVER_DOCKER_HARDENING` | `true` (main `langflowai/langflow` image only) | `false` |
+
+These image values match the [component hardening for untrusted users](/api-keys-and-authentication#multi-tenant-component-hardening) recommendation.
+They apply whether you use `docker run`, Docker Compose, or Kubernetes with the published image, unless you override them.
+
+The image sets `LANGFLOW_AUTO_LOGIN=false`, so you must set `LANGFLOW_SUPERUSER_PASSWORD` (and optionally, `LANGFLOW_SUPERUSER`) unless you explicitly set `LANGFLOW_AUTO_LOGIN=true`.
+
+To disable the stricter defaults and use custom components, built-in code-execution components, or absolute local file paths, override the image defaults:
+
+```bash
+docker run -p 7860:7860 \
+  -e LANGFLOW_AUTO_LOGIN=true \
+  -e LANGFLOW_ALLOW_CUSTOM_COMPONENTS=true \
+  -e LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS=false \
+  -e LANGFLOW_RESTRICT_LOCAL_FILE_ACCESS=false \
+  -e LANGFLOW_MCP_SERVER_DOCKER_HARDENING=false \
+  langflowai/langflow:latest
+```
+
+In Docker Compose, add the same keys under `services.langflow.environment`.
+
+For more information, see [Component hardening for untrusted users](/api-keys-and-authentication#multi-tenant-component-hardening) and [Block custom components](/deployment-block-custom-components).