From aaff8232b0869539a2f9011c8e2ddf73b8cbfb18 Mon Sep 17 00:00:00 2001 From: Simon Smith Date: Thu, 18 Jan 2024 22:33:57 +0000 Subject: [PATCH] fix notes in docs --- docs/docs/meshcentral/index.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/docs/meshcentral/index.md b/docs/docs/meshcentral/index.md index 161ad705..be0834e7 100644 --- a/docs/docs/meshcentral/index.md +++ b/docs/docs/meshcentral/index.md @@ -828,10 +828,10 @@ In this example, we will: - NGINX will be setup with long timeouts, because agents have long standard web socket connections. !!!note - With SELinux, NGINX reverse proxy requires 'setsebool -P httpd_can_network_relay 1' - Caution: httpd_can_network_relay only allows certain ports - Confirm you are using ports from this subset in MeshCentral - If you want to use a different port then you will need to add it to http_port_t + With SELinux, NGINX reverse proxy requires 'setsebool -P httpd_can_network_relay 1' + Caution: httpd_can_network_relay only allows certain ports + Confirm you are using ports from this subset in MeshCentral + If you want to use a different port then you will need to add it to http_port_t Let’s get started by configuring MeshCentral with the following values in config.json: @@ -1658,7 +1658,8 @@ The callback URL will be of the form “https://(servername)/auth-saml-callback Enabling SAML will require MeshCentral to install extra modules from NPM, so depending on your server configuration, you may need to run MeshCentral once manually. !!!note - MeshCentral only supports "POST". [For example Authentik's](https://github.com/Ylianst/MeshCentral/issues/4725) default setting is to use "Redirect" as a "Service Provider Binding". + MeshCentral only supports "POST". [For example Authentik's](https://github.com/Ylianst/MeshCentral/issues/4725) default setting is to use "Redirect" as a "Service Provider Binding". + ## Improvements to MeshCentral In 2007, the first version of MeshCentral was built. We will refer to it as “MeshCentral1”. When MeshCentral1 was designed, HTML5 did not exist and web sockets where not implemented in any of the major browsers. Many design decisions were made at the time that are no longer optimal today. With the advent of the latest MeshCentral, MeshCentral1 is no longer supported and MeshCentral v2 has been significantly redesigned and mostly re-written based of previous version. Here is a list of improvements made in MeshCentral when compared with MeshCentral1: