From 3c19138e125bad3961349d0e7fb505d15d01505f Mon Sep 17 00:00:00 2001 From: Lasantha Samarakoon Date: Mon, 20 Jul 2026 10:12:32 +0530 Subject: [PATCH] Escape Jinja templating syntax in asgardeo-setup.md --- en/docs/next/ai-workspace/authentication/asgardeo-setup.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/en/docs/next/ai-workspace/authentication/asgardeo-setup.md b/en/docs/next/ai-workspace/authentication/asgardeo-setup.md index 70c08c357..bdffa7901 100644 --- a/en/docs/next/ai-workspace/authentication/asgardeo-setup.md +++ b/en/docs/next/ai-workspace/authentication/asgardeo-setup.md @@ -116,6 +116,7 @@ Asgardeo uses `org_id` as the claim for the organization UUID, while the Platfor Update `config.toml`: +{% raw %} ```toml domain = "" auth_mode = "oidc" @@ -137,10 +138,11 @@ organization_claim_name = "org_id" org_name_claim_name = "org_name" org_handle_claim_name = "org_handle" ``` +{% endraw %} `redirect_url` must exactly match the authorized redirect URL you registered in step 2. -Never write the client secret as a literal in `config.toml` — the `{{ env }}` placeholder above reads it from an environment variable instead, so it never has to be committed to source control: +Never write the client secret as a literal in `config.toml` — the {% raw %}`{{ env }}`{% endraw %} placeholder above reads it from an environment variable instead, so it never has to be committed to source control: ```bash export APIP_AIW_OIDC_CLIENT_SECRET=