From d37f0258818b7a359c391fe00ec47769d92b4738 Mon Sep 17 00:00:00 2001 From: Tana M Berry Date: Wed, 30 Apr 2025 17:43:06 -0500 Subject: [PATCH] tweak --- website/docs/add-secure-apps/providers/oauth2/device_code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/add-secure-apps/providers/oauth2/device_code.md b/website/docs/add-secure-apps/providers/oauth2/device_code.md index 9d39e17d5d..bfe39257e7 100644 --- a/website/docs/add-secure-apps/providers/oauth2/device_code.md +++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md @@ -8,7 +8,7 @@ The device code flow is also known as device flow or device authorization grant This device flow is only possible if the active [brand](../../../sys-mgmt/brands.md) has a device code flow configured. This flow is run _after_ the user logs in, and before the user authenticates. -authentik does not include a default flow for this use case, so it is necessary to create a new one with the **Designation** of `Stage Configuration`. +authentik does not include a default flow for this use case, so it is necessary to create a new one with a **Designation** of `Stage Configuration`. ### Device flow initiation