Add zitadel documentation
@@ -14,3 +14,4 @@ List of available guides:
|
|||||||
- [Auth0](/integrations/identity-providers/self-hosted/using-netbird-with-auth0) (managed service)
|
- [Auth0](/integrations/identity-providers/self-hosted/using-netbird-with-auth0) (managed service)
|
||||||
- [Azure AD](/integrations/identity-providers/self-hosted/using-netbird-with-azure-ad) (managed service)
|
- [Azure AD](/integrations/identity-providers/self-hosted/using-netbird-with-azure-ad) (managed service)
|
||||||
- [Keycloak](/integrations/identity-providers/self-hosted/using-netbird-with-keycloak)
|
- [Keycloak](/integrations/identity-providers/self-hosted/using-netbird-with-keycloak)
|
||||||
|
- [Zitadel](/integrations/identity-providers/self-hosted/using-netbird-with-zitadel)
|
||||||
|
|||||||
163
docs/integrations/identity-providers/self-hosted/zitadel.md
Normal file
@@ -0,0 +1,163 @@
|
|||||||
|
---
|
||||||
|
id: using-netbird-with-zitadel
|
||||||
|
title: Using NetBird with Zitadel
|
||||||
|
sidebar_position: 5
|
||||||
|
tags:
|
||||||
|
- integrations
|
||||||
|
- idp
|
||||||
|
- zitadel
|
||||||
|
- oidc
|
||||||
|
- how-to
|
||||||
|
---
|
||||||
|
|
||||||
|
This guide is a part of the [NetBird Self-hosting Guide](/getting-started/self-hosting) and explains how to integrate
|
||||||
|
**self-hosted** NetBird with [Zitadel](https://zitadel.com).
|
||||||
|
|
||||||
|
:::tip managed idp
|
||||||
|
If you prefer not to self-host an Identity and Access Management solution, then you could use a managed alternative like
|
||||||
|
[Auth0](/integrations/identity-providers/self-hosted/using-netbird-with-auth0).
|
||||||
|
:::
|
||||||
|
|
||||||
|
### 1. Create and configure Zitadel application
|
||||||
|
In this step, we will create and configure Netbird application in zitadel.
|
||||||
|
|
||||||
|
Create new zitadel project
|
||||||
|
- Navigate to zitadel console
|
||||||
|
- Click `Projects` at the top menu, then click `Create New Project` to create a new project
|
||||||
|
- Fill in the form with the following values and click `Continue`
|
||||||
|
- Name: `NETBIRD`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Create new zitadel application
|
||||||
|
- Click `Projects` in the top menu and select `NETBIRD` project from the list
|
||||||
|
- Click `New` in `APPLICATIONS` section to create a new application
|
||||||
|
- Fill in the form with the following values and click `Continue`
|
||||||
|
- Name: `netbird`
|
||||||
|
- TYPE OF APPLICATION: `User Agent`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
- Fill in the form with the following values and click `Continue`
|
||||||
|
- Authentication Method: `PKCE`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
- Fill in the form with the following values and click `Continue`
|
||||||
|
- Redirect URIs: `https://<domain>/auth` and click `+`
|
||||||
|
- Post Logout URIs: `https://<domain>/silent-auth` and click `+`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
- Verify applications details and Click `Create` and then click `Close`
|
||||||
|
- Check `Refresh Token` checkbox and click `Save`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
- Copy `Client ID` will be used later in the `setup.env`
|
||||||
|
|
||||||
|
### Step 2: Application Token Configuration
|
||||||
|
|
||||||
|
To configure `netbird` application token you need to:
|
||||||
|
|
||||||
|
- Click `Projects` in the top menu and select `NETBIRD` project from the list
|
||||||
|
- Select `netbird` application from `APPLICATIONS` section
|
||||||
|
- Click `Token Settings` in the left menu
|
||||||
|
- Fill in the form with the following values:
|
||||||
|
- Auth Token Type: `JWT`
|
||||||
|
- Check `Add user roles to the access token` checkbox
|
||||||
|
- Click `Save`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
### Step 3: Application Redirect Configuration
|
||||||
|
|
||||||
|
:::caution
|
||||||
|
This step is intended for setup running in development mode with no SSL
|
||||||
|
:::
|
||||||
|
|
||||||
|
To configure `netbird` application redirect you need to:
|
||||||
|
|
||||||
|
- Click `Projects` in the top menu and select `NETBIRD` project from the list
|
||||||
|
- Select `netbird` application from `APPLICATIONS` section
|
||||||
|
- Click `Redirect Settings` in the left menu
|
||||||
|
- Fill in the form with the following values:
|
||||||
|
- Toggle `Development Mode`
|
||||||
|
- Click `Save`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
### Step 4: Create a Service User
|
||||||
|
|
||||||
|
In this step we will create a `netbird` service user.
|
||||||
|
|
||||||
|
- Click `Users` in the top menu
|
||||||
|
- Select `Service Users` tab
|
||||||
|
- Click `New`
|
||||||
|
- Fill in the form with the following values:
|
||||||
|
- User Name: `netbird`
|
||||||
|
- Name: `netbird`
|
||||||
|
- Description: `Netbird Service User`
|
||||||
|
- Access Token Type: `JWT`
|
||||||
|
- Click `Create`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
In this step we will generate `ClientSecret` for the `netbird` service user.
|
||||||
|
|
||||||
|
- Click `Actions` in the top right corner and click `Generate Client Secret`
|
||||||
|
- Copy `ClientSecret` from the dialog will be used later to set `ClientSecret` in the `management.json`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
### Step 5: Grant manage-users role to netbird service user
|
||||||
|
|
||||||
|
In this step we will grant `Org User Manager` role to `netbird` service user.
|
||||||
|
|
||||||
|
- Click `Organization` in the top menu
|
||||||
|
- Click `+` in the top right corner
|
||||||
|
- Search for `netbird` service user
|
||||||
|
- Check `Org User Manager` checkbox
|
||||||
|
- Click `Add`
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
|
||||||
|
Your authority OIDC configuration will be available under:
|
||||||
|
```
|
||||||
|
https://<YOUR-ZITADEL-HOST-AND-PORT>/.well-known/openid-configuration
|
||||||
|
```
|
||||||
|
:::caution
|
||||||
|
Double-check if the endpoint returns a JSON response by calling it from your browser.
|
||||||
|
:::
|
||||||
|
|
||||||
|
- Set properties in the `setup.env` file:
|
||||||
|
```json
|
||||||
|
NETBIRD_AUTH_OIDC_CONFIGURATION_ENDPOINT="https://<YOUR-ZITADEL-HOST-AND-PORT>/.well-known/openid-configuration"
|
||||||
|
NETBIRD_USE_AUTH0=false
|
||||||
|
NETBIRD_AUTH_CLIENT_ID="<Client ID>"
|
||||||
|
NETBIRD_AUTH_AUDIENCE="<Client ID>"
|
||||||
|
NETBIRD_AUTH_DEVICE_AUTH_CLIENT_ID="<Client ID>"
|
||||||
|
NETBIRD_AUTH_REDIRECT_URI="/auth"
|
||||||
|
NETBIRD_AUTH_SILENT_REDIRECT_URI="/silent-auth"
|
||||||
|
```
|
||||||
|
|
||||||
|
- You can now continue with the [NetBird Self-hosting Guide](/getting-started/self-hosting#step-3-configure-identity-provider).
|
||||||
|
|
||||||
|
- Set property `IdpManagerConfig` in the `management.json` file with:
|
||||||
|
:::caution
|
||||||
|
The file management.json is created automatically. Please refer [here](/getting-started/self-hosting#step-5-run-configuration-script) for more information.
|
||||||
|
:::
|
||||||
|
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"ManagerType": "zitadel",
|
||||||
|
"ZitadelClientCredentials": {
|
||||||
|
"ClientID": "netbird",
|
||||||
|
"ClientSecret": "<CLIENT SECRET>",
|
||||||
|
"GrantType": "client_credentials",
|
||||||
|
"TokenEndpoint": "https://<YOUR-ZITADEL-HOST-AND-PORT>/oauth/v2/token",
|
||||||
|
"ManagementEndpoint": "https://<YOUR-ZITADEL-HOST-AND-PORT>/management/v1"
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
After Width: | Height: | Size: 100 KiB |
|
After Width: | Height: | Size: 141 KiB |
|
After Width: | Height: | Size: 168 KiB |
|
After Width: | Height: | Size: 109 KiB |
|
After Width: | Height: | Size: 200 KiB |
|
After Width: | Height: | Size: 86 KiB |
|
After Width: | Height: | Size: 147 KiB |
|
After Width: | Height: | Size: 214 KiB |
|
After Width: | Height: | Size: 126 KiB |
|
After Width: | Height: | Size: 158 KiB |