New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature Request: Secure the webinterface #2021

Open

scoopex opened this issue Nov 16, 2024 · 0 comments

scoopex commented Nov 16, 2024

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)

scoopex changed the title ~~Secure the webinterface~~ Feature Request: Secure the webinterface

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment