From c68a42f63bad68bd63f995e95d53097e2eade739 Mon Sep 17 00:00:00 2001 From: Jens L Date: Wed, 10 May 2023 20:58:31 +0200 Subject: [PATCH] website/docs: improve docs for OAuth2 device code flow (#5570) Signed-off-by: Jens Langhammer --- website/docs/providers/oauth2/device_code.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/providers/oauth2/device_code.md b/website/docs/providers/oauth2/device_code.md index eed7615f4..f99029953 100644 --- a/website/docs/providers/oauth2/device_code.md +++ b/website/docs/providers/oauth2/device_code.md @@ -1,6 +1,6 @@ # Device code flow -(Also known as device flow and RFC 8628) +(Also known as device flow and [RFC 8628](https://datatracker.ietf.org/doc/html/rfc8628)) This type of authentication flow is useful for devices with limited input abilities and/or devices without browsers. @@ -8,6 +8,8 @@ This type of authentication flow is useful for devices with limited input abilit This device flow is only possible if the active tenant has a device code flow setup. This device code 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 recommended to create a new flow for this usecase with the designation of _Stage configuration_ + ### Device-side The flow is initiated by sending a POST request to the device authorization endpoint, `/application/o/device/` with the following contents: