Allow basic-auth protection

[dpalic]

Is your feature request related to a problem? Please describe.
to use meshcentral requires to protect it behind a firewall to reduce attack vectors.
VPNs are sometime a solution which is not allowed on high regulated environments.
So a simple additional http-basic auth is already helpful to allow "http proxied" users to access meshcentral.

Describe the solution you'd like
if meshcentral is protected behind a basic auth the router tools are currently not able to be used, as this additional authentication is not supported.
So routers would require a implementation to allow to add a basic auth additionally

Describe alternatives you've considered
VPN => not possible in highly regulated envs

Offer
I can help to provide the required changes for the router apps, if I get some swift and helpful feedback to my impls.

[si458]

@dpalic i dont quite understand what you want, what do you mean basic auth?
meshcentral has a login page and supports 2FA
meshcentral supports only allowing access from certain ip addresses userAllowedIP and agentAllowedIP
the router application (and websockets api etc) all use the x-meshauth: (base64 username),(base64 password) http headers?

[fz0000]

Do you mean you want to use the standard HTTP basic authentication (i.e. use https://user:password@meshcentral.mydomain.com or use the http header Authorization: Basic base64(user:password) to log in) ?

I guess some proxy servers might modify or strip custom HTTP headers (e.g. x-meshauth), whereas the Authorization header is typically left untouched.

[si458]

@fz0000 that makes sense but are they talking about the websocket /control.ashx or the web ui?
The websocket would be easy to add in but web ui different story