Fix broken links (#92)

This commit is contained in:
Yury Gargay
2023-09-26 11:12:06 +02:00
committed by GitHub
parent b54abbfa79
commit 897a6cc971
3 changed files with 10 additions and 10 deletions

View File

@@ -47,7 +47,7 @@ We use [Carrier Grade NAT](https://en.wikipedia.org/wiki/Carrier-grade_NAT) addr
Whenever a new peer joins the network, all other peers that are authorized to connect to it receive an update. Whenever a new peer joins the network, all other peers that are authorized to connect to it receive an update.
After that, they are able to establish a connection to the new peer. After that, they are able to establish a connection to the new peer.
* **Creating and managing access control rules.** * **Creating and managing access control rules.**
* **Managing private DNS.** [DNS](docs/how-to/manage-dns-in-your-network) allows referring to each of the peers with a fully qualified domain name (FQDN). * **Managing private DNS.** [DNS](/how-to/manage-dns-in-your-network) allows referring to each of the peers with a fully qualified domain name (FQDN).
* **Logging network activity.** * **Logging network activity.**
* **Wireguard key rotation.** <em>Coming Soon</em>. * **Wireguard key rotation.** <em>Coming Soon</em>.
@@ -67,7 +67,7 @@ The Client's roles are the following:
* **Generating private and public Wireguard keys.** These keys are used for packet encryption between peers and for [Wireguard Cryptokey Routing](https://www.wireguard.com/#cryptokey-routing). * **Generating private and public Wireguard keys.** These keys are used for packet encryption between peers and for [Wireguard Cryptokey Routing](https://www.wireguard.com/#cryptokey-routing).
To accept the incoming connections, peers have to know each other, therefore, the generated public keys have to be pre-shared on the machines. The client application sends its public key to the Management service which then distributes it to the authorized peers. To accept the incoming connections, peers have to know each other, therefore, the generated public keys have to be pre-shared on the machines. The client application sends its public key to the Management service which then distributes it to the authorized peers.
* **Handling peer registration and authentication.** Each peer has to be authenticated and registered in the system. The client application requests a user to log in with an Identity Provider (IDP) or a [setup key](/overview/setup-keys) so that the peer can be associated with the organization's account. * **Handling peer registration and authentication.** Each peer has to be authenticated and registered in the system. The client application requests a user to log in with an Identity Provider (IDP) or a [setup key](/how-to/register-machines-using-setup-keys) so that the peer can be associated with the organization's account.
* **Receiving network updates from the Management service.** * **Receiving network updates from the Management service.**
Each peer receives initial configuration and a list of peers with corresponding public keys and IP addresses so that it can establish a peer-to-peer connection. Each peer receives initial configuration and a list of peers with corresponding public keys and IP addresses so that it can establish a peer-to-peer connection.
* **Establishing peer-to-peer Wireguard connection.** To establish a connection with a remote peer, the Client first discovers the most suitable connection candidate, or simply address (IP:port) that other peer can use to connect to it. * **Establishing peer-to-peer Wireguard connection.** To establish a connection with a remote peer, the Client first discovers the most suitable connection candidate, or simply address (IP:port) that other peer can use to connect to it.

View File

@@ -190,7 +190,7 @@ Keycloak is an open source software product to allow single sign-on with Identit
<Note> <Note>
If you prefer not to self-host an Identity and Access Management solution, then you could use a managed alternative like 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). [Auth0](/selfhosted/identity-providers#auth0).
</Note> </Note>
The following guide is an adapted version of the original The following guide is an adapted version of the original
@@ -443,7 +443,7 @@ This guide is a part of the [NetBird Self-hosting Guide](/docs/selfhosted/selfho
<Note> <Note>
If you prefer not to self-host an Identity and Access Management solution, then you could use a managed alternative like 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). [Auth0](/selfhosted/identity-providers#auth0).
</Note> </Note>
#### Step 1: Create OAuth2/OpenID Provider #### Step 1: Create OAuth2/OpenID Provider
@@ -564,7 +564,7 @@ It is a 3rd party managed service and can't be self-hosted.
<Note> <Note>
If you prefer to have full control over authentication and authorization of your NetBird network, there are good If you prefer to have full control over authentication and authorization of your NetBird network, there are good
self-hosted alternatives to the managed Auth0 service like [Keycloak](/integrations/identity-providers/self-hosted/using-netbird-with-keycloak). self-hosted alternatives to the managed Auth0 service like [Keycloak](/selfhosted/identity-providers#keycloak).
</Note> </Note>
Before you start creating and configuring an Azure AD application, ensure that you have the following: Before you start creating and configuring an Azure AD application, ensure that you have the following:
@@ -718,11 +718,11 @@ You've configured all required resources in Azure AD. You can now continue with
### Okta ### Okta
This guide is a part of the [NetBird Self-hosting Guide](/getting-started/self-hosting) and explains how to integrate This guide is a part of the [NetBird Self-hosting Guide](/selfhosted/selfhosted-guide) and explains how to integrate
**self-hosted** NetBird with [Okta](https://www.okta.com/). **self-hosted** NetBird with [Okta](https://www.okta.com/).
<Note> <Note>
If you prefer to have full control over authentication and authorization of your NetBird network, there are good self-hosted alternatives to the managed Okta service like [Keycloak](/integrations/identity-providers/self-hosted/using-netbird-with-keycloak). If you prefer to have full control over authentication and authorization of your NetBird network, there are good self-hosted alternatives to the managed Okta service like [Keycloak](/selfhosted/identity-providers#keycloak).
</Note> </Note>
Before you start creating and configuring an Okta application, ensure that you have an Okta workforce identity cloud account. If you don't have one, sign up for a free account at https://www.okta.com/free-trial/. Before you start creating and configuring an Okta application, ensure that you have an Okta workforce identity cloud account. If you don't have one, sign up for a free account at https://www.okta.com/free-trial/.
@@ -846,7 +846,7 @@ You've configured all required resources in Okta. You can now continue with the
### Google Workspace ### Google Workspace
This guide is a part of the [NetBird Self-hosting Guide](/getting-started/self-hosting) and explains how to integrate This guide is a part of the [NetBird Self-hosting Guide](/selfhosted/selfhosted-guide) and explains how to integrate
**self-hosted** NetBird with [Google Workspace](https://workspace.google.com/). **self-hosted** NetBird with [Google Workspace](https://workspace.google.com/).
Before you start creating and configuring an Google Workspace application, ensure that you have the following: Before you start creating and configuring an Google Workspace application, ensure that you have the following:
@@ -1007,7 +1007,7 @@ instance on your own.
<Note> <Note>
If you prefer to have full control over authentication and authorization of your NetBird network, there are good If you prefer to have full control over authentication and authorization of your NetBird network, there are good
self-hosted alternatives to the managed Auth0 service like [Keycloak](/integrations/identity-providers/self-hosted/using-netbird-with-keycloak). self-hosted alternatives to the managed Auth0 service like [Keycloak](/selfhosted/identity-providers#keycloak).
</Note> </Note>
#### Step 1: Create Auth0 account #### Step 1: Create Auth0 account

View File

@@ -18,7 +18,7 @@ as the identity provider for user management using a single-line setup script an
<Note> <Note>
This is the quickest way to try self-hosted NetBird. It should take around 5 minutes to get started if you already have a public domain and a VM. This is the quickest way to try self-hosted NetBird. It should take around 5 minutes to get started if you already have a public domain and a VM.
Follow the [Advanced guide with a custom identity provider](#advanced-guide-with-a-custom-identity-provider) for installations with different IDPs. Follow the [Advanced guide with a custom identity provider](/selfhosted/selfhosted-guide#advanced-self-hosting-guide-with-a-custom-identity-provider) for installations with different IDPs.
</Note> </Note>
### Requirements ### Requirements