netbird/management
Maycon Santos fec3132585
Adding peer registration support to JWT (#305)
The management will validate the JWT as it does in the API
 and will register the Peer to the user's account.

New fields were added to grpc messages in management
 and client daemon and its clients were updated

Peer has one new field, UserID, 
that will hold the id of the user that registered it

JWT middleware CheckJWT got a splitter 
and renamed to support validation for non HTTP requests

Added test for adding new Peer with UserID

Lots of tests update because of a new field
2022-05-05 20:02:15 +02:00
..
client Adding peer registration support to JWT (#305) 2022-05-05 20:02:15 +02:00
cmd Rename module to netbirdio/netbird (#288) 2022-03-26 12:08:54 +01:00
proto Adding peer registration support to JWT (#305) 2022-05-05 20:02:15 +02:00
server Adding peer registration support to JWT (#305) 2022-05-05 20:02:15 +02:00
Dockerfile feature: add logging to a file (#112) 2021-09-07 09:53:18 +02:00
Dockerfile.debug feature: add logging to a file (#112) 2021-09-07 09:53:18 +02:00
main.go Rename module to netbirdio/netbird (#288) 2022-03-26 12:08:54 +01:00
README.md Replace Wiretrustee links and naming (#287) 2022-03-26 11:39:27 +01:00

netbird Management Server

netbird management server will control and synchronize peers configuration within your wiretrustee account and network.

Command Options

The CLI accepts the command management with the following options:

start Wiretrustee Management Server

Usage:
  wiretrustee-mgmt management [flags]

Flags:
      --datadir string              server data directory location (default "/var/lib/wiretrustee/")
  -h, --help                        help for management
      --letsencrypt-domain string   a domain to issue Let's Encrypt certificate for. Enables TLS using Let's Encrypt. Will fetch and renew certificate, and run the server with TLS
      --port int                    server port to listen on (default 33073)
      --cert-file string            Location of your SSL certificate. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect
      --cert-key string             Location of your SSL certificate private key. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect
Global Flags:
      --config string      Wiretrustee config file location to write new config to (default "/etc/wiretrustee/config.json")
      --log-level string    (default "info")
      --log-file string    sets Wiretrustee log path. If console is specified the the log will be output to stdout (default "/var/log/wiretrustee/management.log")

Run Management service (Docker)

You can run service in 2 modes - with TLS or without (not recommended).

Run with TLS (Let's Encrypt).

By specifying the --letsencrypt-domain the daemon will handle SSL certificate request and configuration.

In the following example 33073 is the management service default port, and 443 will be used as port for Let's Encrypt challenge and HTTP API.

The server where you are running a container has to have a public IP (for Let's Encrypt certificate challenge).

Replace with your server's public domain (e.g. mydomain.com or subdomain sub.mydomain.com).

# create a volume
docker volume create wiretrustee-mgmt
# run the docker container
docker run -d --name wiretrustee-management \
-p 33073:33073  \
-p 443:443  \
-v wiretrustee-mgmt:/var/lib/wiretrustee  \
-v ./config.json:/etc/wiretrustee/config.json  \
wiretrustee/management:latest \
--letsencrypt-domain <YOUR-DOMAIN>

An example of config.json can be found here management.json

Trigger Let's encrypt certificate generation:

curl https://<YOUR-DOMAIN>

The certificate will be persisted in the datadir/letsencrypt/ folder (e.g. /var/lib/wiretrustee/letsencrypt/) inside the container.

Make sure that the datadir is mapped to some folder on a host machine. In case you used the volume command, you can run the following to retrieve the Mountpoint:

docker volume inspect wiretrustee-mgmt
[
    {
        "CreatedAt": "2021-07-25T20:45:28Z",
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/volumes/mgmt/_data",
        "Name": "wiretrustee-mgmt",
        "Options": {},
        "Scope": "local"
    }
]

Consequent restarts of the container will pick up previously generated certificate so there is no need to trigger certificate generation with the curl command on every restart.

Run without TLS.

# create a volume
docker volume create wiretrustee-mgmt
# run the docker container
docker run -d --name wiretrustee-management \
-p 33073:33073  \
-v wiretrustee-mgmt:/var/lib/wiretrustee  \
-v ./config.json:/etc/wiretrustee/config.json  \
wiretrustee/management:latest

Debug tag

We also publish a docker image with the debug tag which has the log-level set to default, plus it uses the gcr.io/distroless/base:debug image that can be used with docker exec in order to run some commands in the Management container.

shell $ docker run -d --name wiretrustee-management-debug \
-p 33073:33073  \
-v wiretrustee-mgmt:/var/lib/wiretrustee  \
-v ./config.json:/etc/wiretrustee/config.json  \
wiretrustee/management:debug-latest

shell $ docker exec -ti wiretrustee-management-debug /bin/sh
container-shell $ 

For development purposes:

Install golang gRpc tools:

#!/bin/bash
go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.26
go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.1

Generate gRpc code:

#!/bin/bash
protoc -I proto/ proto/management.proto --go_out=. --go-grpc_out=.