From 370eff14945e3e05b066ee357ac83de13f0e6659 Mon Sep 17 00:00:00 2001
From: Nate Fonseka <882236+nfons@users.noreply.github.com>
Date: Tue, 8 Apr 2025 09:24:46 -0400
Subject: [PATCH] website/integrations: fix ArgoCD redirect paths (#13804)

---
 website/integrations/services/argocd/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/integrations/services/argocd/index.md b/website/integrations/services/argocd/index.md
index 5521e2e79a..de5d9d95e1 100644
--- a/website/integrations/services/argocd/index.md
+++ b/website/integrations/services/argocd/index.md
@@ -34,7 +34,7 @@ To support the integration of ArgoCD with authentik, you need to create an appli
 - **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
 - **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.
-    - Add two `Strict` redirect URI and set them to <kbd>https://<em>argocd.company</em>/api/dex/callback/</kbd> and <kbd>https://<em>localhost:8085</em>/auth/callback/</kbd>.
+    - Add two `Strict` redirect URI and set them to <kbd>https://<em>argocd.company</em>/api/dex/callback</kbd> and <kbd>https://<em>localhost:8085</em>/auth/callback</kbd>.
     - 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.