From 149815885d53bfca54d39fa0ad63317f50bea793 Mon Sep 17 00:00:00 2001 From: Tana M Berry Date: Wed, 30 Apr 2025 17:23:48 -0500 Subject: [PATCH] final tweaks --- .../docs/add-secure-apps/providers/oauth2/device_code.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) 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 d51333de20..9d39e17d5d 100644 --- a/website/docs/add-secure-apps/providers/oauth2/device_code.md +++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md @@ -10,9 +10,9 @@ This device flow is only possible if the active [brand](../../../sys-mgmt/brands 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`. -### Device-side +### Device flow initiation -The flow is initiated by sending a POST request to the device authorization endpoint, `/application/o/device/` with the following contents: +The flow is initiated by sending a POST request to the device authorization endpoint, `/application/o/device/`, with the following contents: ```http POST /application/o/device/ HTTP/1.1 @@ -32,8 +32,6 @@ The response contains the following fields: - `expires_in`: The total seconds after which this token will expire - `interval`: The interval in seconds for how often the device should check the token status ---- - With this response, the device can start checking the status of the token by sending requests to the token endpoint like this: ```http