From ce1fc4eef41b132fef1abbbfdf2c574da9ae559a Mon Sep 17 00:00:00 2001 From: Dewi Roberts Date: Sun, 5 Oct 2025 14:22:55 +0100 Subject: [PATCH] website/integrations: fix mealie (#17250) Adds mention of signing key because mealie requires it --- website/integrations/documentation/mealie/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/integrations/documentation/mealie/index.md b/website/integrations/documentation/mealie/index.md index 783ac7544a..c7ed167ca6 100644 --- a/website/integrations/documentation/mealie/index.md +++ b/website/integrations/documentation/mealie/index.md @@ -35,6 +35,7 @@ To support the integration of Mealie with authentik, you need to create an appli - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations. - Note the **Client ID**, **Client Secret**, , and **slug** values because they will be required later. - Create two `Strict` redirect URIs and set to `https://mealie.company/login` and `https://mealie.company/login?direct=1`. + - Select any available signing key. - **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page. 3. Click **Submit** to save the new application and provider.