29f53fd3a4
* new topics * update diagram * more writing and sidebar entries * fix file name * more link fixes * fix header level * Optimised images with calibre/image-actions * rewrite stuff Signed-off-by: Jens Langhammer <jens@goauthentik.io> * reorganize more Signed-off-by: Jens Langhammer <jens@goauthentik.io> * messed w/ diagram and added 3 categories * fixed anchor * removed whole line * add link * more rearrangements * more content * edits * more polishes, rest of Jens' knowledge dump * more content * tweaks * tweak * argh * synch with main * tweaks to test merge * cleanup * offline_access * polish --------- Signed-off-by: Jens Langhammer <jens@goauthentik.io> Co-authored-by: Tana M Berry <tana@goauthentik.com> Co-authored-by: authentik-automation[bot] <135050075+authentik-automation[bot]@users.noreply.github.com> Co-authored-by: Jens Langhammer <jens@goauthentik.io>
20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
---
|
|
title: Create an OAuth2 provider
|
|
---
|
|
|
|
To add a provider (and the application that uses the provider for authentication) use the Application Wizard, which creates both the new application and the required provider at the same time. For typical scenarios, authentik recommends that you use the Wizard to create both the application and the provider together. (Alternatively, use our legacy process: navigate to **Applications --> Providers**, and then click **Create**.)
|
|
|
|
1. Log into authentik as an admin, and navigate to **Applications --> Applications**.
|
|
|
|
2. Click **Create with Wizard**.
|
|
|
|
3. In the **New application** wizard, define the application details, and then click **Next**.
|
|
|
|
4. Select the **Provider Type** of **OAuth2/OIDC**, and then click **Next**.
|
|
|
|
5. On the **Configure OAuth2/OpenId Provider** page, provide the configuration settings and then click **Submit** to create and save both the application and the provider.
|
|
|
|
:::info
|
|
Optionally, configure the provider to have the `offline_access` scope mapping. Starting with authentik 2024.2, by default applications only receive an access token. To receive a refresh token, both applications and authentik must be configured to request the `offline_access` scope. Do this in the Scope mapping area on the **Configure OAuth2/OpenId Provider** page.
|
|
:::
|