From 1c022cb366f7275d080c9dc479a313c4422b597c Mon Sep 17 00:00:00 2001 From: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com> Date: Sat, 26 Apr 2025 19:53:13 +0200 Subject: [PATCH] Update website/docs/add-secure-apps/providers/oauth2/device_code.md Co-authored-by: Dominic R Signed-off-by: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com> --- 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 1dbdbb3940..58f0c9a87e 100644 --- a/website/docs/add-secure-apps/providers/oauth2/device_code.md +++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md @@ -17,7 +17,7 @@ This type of authentication flow is useful for devices with limited input capabi This device flow is only possible if the active [brand](../../../sys-mgmt/brands.md) has a device code flow setup. This flow is run _after_ the user logs in, and before the user authenticates. -authentik doesn't ship with a default flow for this usecase, so it is required to create a new flow for this usecase 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 the **Designation** of **Stage Configuration**. ### Steps