Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions src/pages/selfhosted/identity-providers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -536,17 +536,28 @@ In this step, we will add `Netbird` service account to `authentik Admins` group.
</p>

#### Step 5: Create a authentication flow for device token authentication
Navigate to Authentik admin interface > Flows & Stages > Flows > Create

- Navigate to authentik admin interface
- Click `Flows and Stages` on the left menu, then click `Flows` then `Create`
- Fill in the form with the following values and click `Create`
- Name: `default-device-code-flow`
- Title: `Device Code Flow`
- Designation: `Stage Configuration`
- Authentication: `Require authentication`

<p>
<img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-new-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
</p>

- Navigate to authentik admin interface
- Click `System` on the left menu, then click `Brands`
- Click on the edit button of domain `authentik-default`
- Under Default flows set Device code flow to `default-device-code-flow`
- Click `Update`

Then go to: System > Brands > Edit used default > Default Flows > set **Device code flow** to newly created device flow
<p>
<img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-brand-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
</p>
Press `Update`

Your authority OIDC configuration will be available under:

Expand Down
Loading