From df5e819472b5c8f762762f051b1c447a01a31fee Mon Sep 17 00:00:00 2001 From: Taylor Wilsdon Date: Mon, 7 Apr 2025 15:39:14 -0400 Subject: [PATCH] fix last block close --- docs/tutorials/integrations/okta-oidc-sso.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/integrations/okta-oidc-sso.md b/docs/tutorials/integrations/okta-oidc-sso.md index 258993c..64c641a 100644 --- a/docs/tutorials/integrations/okta-oidc-sso.md +++ b/docs/tutorials/integrations/okta-oidc-sso.md @@ -90,6 +90,7 @@ Replace `YOUR_OKTA_CLIENT_ID`, `YOUR_OKTA_CLIENT_SECRET`, and `YOUR_OKTA_OIDC_DI :::info Session Persistence in Multi-Node Deployments When deploying Open WebUI across multiple nodes (e.g., in a Kubernetes cluster or behind a load balancer), it is crucial to ensure session persistence for a seamless user experience, especially with SSO. Set the `WEBUI_SECRET_KEY` environment variable to the **same secure, unique value** on **all** Open WebUI instances. +::: ```bash # Example: Generate a strong secret key (e.g., using openssl rand -hex 32) @@ -97,7 +98,6 @@ WEBUI_SECRET_KEY="YOUR_UNIQUE_AND_SECURE_SECRET_KEY" ``` If this key is not consistent across all nodes, users may be forced to log in again if their session is routed to a different node, as the session token signed by one node will not be valid on another. By default, the Docker image generates a random key on first start, which is unsuitable for multi-node setups. -::: :::tip Disabling the Standard Login Form