habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

final tweaks

Browse Source
This commit is contained in:
Tana M Berry
2025-04-30 17:23:48 -05:00
parent be46545613
commit 149815885d
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/add-secure-apps/providers/oauth2/device_code.md
View File

@ -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`. 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 ```http
POST /application/o/device/ HTTP/1.1 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 - `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 - `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: With this response, the device can start checking the status of the token by sending requests to the token endpoint like this:
```http ```http