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

"Relative vs. absolute paths" rule

Browse Source 
Removed full link in favor of relative path

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

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

@ -15,7 +15,7 @@ This type of authentication flow is useful for devices with limited input capabi
### Requirements
This device flow is only possible if the active [brand](https://docs.goauthentik.io/docs/brands) has a device code flow setup. This flow is run _after_ the user logs in, and before the user authenticates.
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`.