Skip to content
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.

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

WEB Gui - is there a way to password protect "active" actions and keep read-only mode for all other users? (TZ-1477) #119

Open
3 tasks done
pczekalski opened this issue Jan 15, 2025 · 0 comments

Comments

@pczekalski
Copy link

Checklist

  • Checked the issue tracker for similar issues to ensure this is not a duplicate.
  • Described the feature in detail and justified the reason for the request.
  • Provided specific use cases and examples.

Feature description

I'm looking for a feature that at least lets me protect the WEB GUI from unauthorised users to modify the device's and network's configuration. It could be achieved either by full protection of the WEB GUI (at least with basic authentication) or, best, by providing two access layers: passive for browsing and active for developers, who might modify the device's and network's configuration.

Use cases

In laboratory scenarios, admins would like to provide regular users with open-thread network information as seen from the border router point of view (e.g., network topology) but not let them re-configure the network or the device via the WEB GUI.

Alternatives

Use of external authentication with e.g. nginx and reverse proxy, but that requires extra infrastructure.

Additional context

No response

@github-actions github-actions bot changed the title WEB Gui - is there a way to password protect "active" actions and keep read-only mode for all other users? WEB Gui - is there a way to password protect "active" actions and keep read-only mode for all other users? (TZ-1477) Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant