diff --git a/src/pages/selfhosted/identity-providers.mdx b/src/pages/selfhosted/identity-providers.mdx index cc1e18ee..df13dd48 100644 --- a/src/pages/selfhosted/identity-providers.mdx +++ b/src/pages/selfhosted/identity-providers.mdx @@ -44,7 +44,7 @@ up until "Install the Auth0 React SDK". - Use **`Client ID`** to set ```NETBIRD_AUTH_CLIENT_ID``` property in the `setup.env` file. - Use **`Domain`** to configure ```NETBIRD_AUTH_OIDC_CONFIGURATION_ENDPOINT``` property in the `setup.env` file like so: -``` +```bash https:///.well-known/openid-configuration ``` @@ -322,7 +322,7 @@ The client will need secret to authenticate. To do this:

Your authority OIDC configuration will be available under: -``` +```bash https:///realms/netbird/.well-known/openid-configuration ``` @@ -482,7 +482,7 @@ In this step, we will create and configure NetBird application in azure AD.

Your authority OIDC configuration will be available under: -``` +```bash https://login.microsoftonline.com//v2.0/.well-known/openid-configuration ``` @@ -661,9 +661,11 @@ In this step we will grant `Org User Manager` role to `netbird` service user.

Your authority OIDC configuration will be available under: -``` + +```bash 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. ::: @@ -791,9 +793,11 @@ In this step, we will add `Netbird` service account to `authentik Admins` group.

Your authority OIDC configuration will be available under: -``` + +```bash https://< YOUR-AUTHENTIK-HOST-AND-PORT >/application/o/netbird/.well-known/openid-configuration ``` + Double-check if the endpoint returns a JSON response by calling it from your browser. @@ -914,7 +918,7 @@ In this step, we will generate netbird api token in okta for authorizing calls t Your authority OIDC configuration will be available under: -``` +```bash https://< your_okta_organization_url >/.well-known/openid-configuration ```