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

Improved RFC reference

Browse Source 
Replaced "abilities" with "capabilities" to better reflect RFC wording, added extended summary from RFC to ensure complete and clear understanding.

Signed-off-by: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
This commit is contained in:
Dametto Luca
2025-04-26 10:09:15 +02:00
committed by Tana M Berry
parent 78345853c2
commit 3b6de494c9
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2,7 +2,16 @@
(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.
This type of authentication flow is useful for devices with limited input capabilities and/or devices without browsers.
> The OAuth 2.0 device authorization grant is designed for Internet-connected
> devices that either lack a browser to perform a user-agent-based
> authorization or are input constrained to the extent that
> requiring the user to input text in order to authenticate during the
> authorization flow is impractical. It enables OAuth clients on such
> devices (like smart TVs, media consoles, digital picture frames, and
> printers) to obtain user authorization to access protected resources
> by using a user agent on a separate device.
### Requirements