Feature Request: Secure the webinterface

[scoopex]

I am running version 2.1.5-Patch.2 and I am wondering why OpenWB has no authentication for the configuration or the web interface in general.

It would be very important to be able to operate OpenWB reasonably securely in shared networks:

• that the configuration can be secured with a ‘manager’ user (e.g. Basic Auth)
• that the user interface of the wallbox that is accessible via the network can be secured with a second password (e.g. Basic Auth)
• that OpenWB is not operated on HTTP but on HTTPS (a default certificate should be generated, possibly replaceable with a other certificate)

[knox]

that OpenWB is not operated on HTTP but on HTTPS (a default certificate should be generated, possibly replaceable with a other certificate)

the web interface is available via TLS with a self-signed certificate, at least with 2.1.7-Patch.3

[benderl]

Done with user management in Master 2.2.0.