|
1 | | -# Authentik |
2 | | - |
3 | | -## Public client configuration |
4 | | -Under construction. |
5 | | - |
6 | | -## Confidential client configuration |
7 | | - |
8 | | -1. From the admin interface, go to `Applications > Providers` and click on `Create` |
9 | | -2. Select `OAuth2/OpenID Provider` and click `Next` |
10 | | -3. Fill the following details: |
11 | | - - Name: `Home Assistant Provider` |
12 | | - - Authorization flow: `default-provider-authorization-explicit-consent` |
13 | | - - Client type: `Confidential` |
14 | | - - Client ID: `homeassistant` |
15 | | - - Client Secret: **Copy this value** |
16 | | - - Redirect URIs/Origins: Click on `Add entry` (You can use either DNS, Internal/External IP or localhost) |
17 | | - - Strict: https://hass.example.com/auth/oidc/callback |
18 | | -4. Click `Finish` to save the provider configuration |
19 | | -5. Open the created Provider |
20 | | -6. On the Assigned to application section click on `Create`: |
21 | | - - Name: `Home Assistant` |
22 | | - - Slug: `home-assistant` |
23 | | - - Provider: `Home Assistant Provider` |
24 | | - |
25 | | - Then save the configuration |
26 | | - |
27 | | -## Home Assistant configuration |
28 | | - |
29 | | -> [!IMPORTANT] |
30 | | -> For HTTPS configuration make sure to have a public valid SSL certificate (i.e. LetsEncrypt), if not, use HTTP instead (more insecure) or add your Authentik CA certificate to `network.tls_ca_path`. |
31 | | -
|
32 | | -After installing this HACS addon, edit your `configuration.yaml` file and add: |
33 | | -```yaml |
34 | | -auth_oidc: |
35 | | - client_id: "homeassistant" |
36 | | - client_secret: "client_secret" |
37 | | - discovery_url: "https://auth.example.com/application/o/home-assistant/.well-known/openid-configuration" |
38 | | -``` |
39 | | -
|
40 | | -Restart Home Assistant and go to https://hass.example.com/auth/oidc/welcome |
| 1 | +# authentik |
| 2 | + |
| 3 | +> [!TIP] |
| 4 | +> This guide describes configuring authentik using the UI method. You can also configure authentik by hand with YAML. Instructions for configuring any provider using YAML can be found here: [YAML Configuration Guide](../configuration.md). |
| 5 | +
|
| 6 | + |
| 7 | +## Step 1. Install the integration |
| 8 | + |
| 9 | +Make sure that you have fully installed the latest release of the integration. The easiest way to install the integration is through [the Home Assistant Community Store (HACS)](https://hacs.xyz/). You can find usage instructions for HACS here: https://hacs.xyz/docs/use/. |
| 10 | + |
| 11 | +After installing HACS, search for "OpenID Connect" in the HACS search box or click the button below: |
| 12 | + |
| 13 | +[](https://my.home-assistant.io/redirect/hacs_repository/?owner=christiaangoossens&repository=hass-oidc-auth&category=Integration) |
| 14 | + |
| 15 | +## Step 2. Configure authentik |
| 16 | + |
| 17 | +1. Log in to authentik as an administrator and open the authentik Admin interface. |
| 18 | + |
| 19 | +2. Navigate to **Applications > Applications** and click **Create with Provider** to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.) |
| 20 | + |
| 21 | + - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. |
| 22 | + - Choose a **Provider Type**: select **OAuth2/OpenID Connect** as the provider type. |
| 23 | + - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations. |
| 24 | + - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later. |
| 25 | + - Set a `Strict` redirect URI to `https://<your HA URL>/auth/oidc/callback`. |
| 26 | + - Select any available signing key (to use the RS256 `id_token_signing_alg`) |
| 27 | + - Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page. |
| 28 | + |
| 29 | +## Step 3. Home Assistant configuration |
| 30 | + |
| 31 | +The recommended setup method for beginners is through the "Integrations" panel within the Home Assistant UI. You can also use YAML setup, for which you can find the configuration guide here: [YAML Configuration Guide](../configuration.md). |
| 32 | + |
| 33 | +1. Open Home Assistant and go to **Settings -> Devices & Services**. |
| 34 | +2. Click Add Integration and select **OpenID Connect/SSO Authentication**. |
| 35 | + |
| 36 | + |
| 37 | + |
| 38 | +3. Now click "Authentik" and continue to the next screen |
| 39 | +4. Set the discovery URL to `https://<your Authentik URL>/application/o/<application_slug>/.well-known/openid-configuration` using the **slug** from the earlier authentik configuration step and click **Submit** |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +5. Your URL will be tested. You may see an error, such as the picture below. Check your URL and verify that Home Assistant can access your authentik installation. Change the URL or retry. |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +6. If your discovery URL is tested succesfully, you will see something like this and you can continue with the **Submit** button to continue. |
| 48 | + |
| 49 | + |
| 50 | + |
| 51 | + |
| 52 | +7. You will then be prompted to fill in the client details, the **Client ID** and the **Client Secret** (if you used the Public Client type in authentik, there is no Client Secret required). Paste them in the relevant input boxes and continue setup with **Submit**. |
| 53 | + |
| 54 | + |
| 55 | + |
| 56 | +8. You will then be asked about **Groups & Role Configuration** and **User Linking**. Configure these options as you wish or leave the defaults in place. You can also change these settings later by opening the integration settings and clicking the reconfiguration icon. |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | +## Done! |
| 62 | + |
| 63 | +You should now automatically see the welcome screen upon opening your Home Assistant URL. On the welcome screen you can choose to either start login through SSO or to use an alternative login method, which will bring you back to the normal Home Assistant username/password login screen. |
0 commit comments