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

Hello, is there a config that allow the user to disable the admin user interface #2870

Open
Nomia opened this issue Mar 10, 2025 · 2 comments

Comments

@Nomia
Copy link

Nomia commented Mar 10, 2025

Hello, is there a config that allow the user to disable the admin user interface?

Currently there is no auth configuration for the admin user interface, our security team worried about the unintentional write operation(e.g. remove/stop a service or add a service) that would break our services or cause chaos, so it would be better if we can:

  1. disable the admin ui
  2. disable the write operation for the admin ui
  3. even disable the admin as a whole(the log reporting & admin ui), if it's possible.(from my understanding that the restate server is essential for all the services, but not the admin)
@Nomia Nomia changed the title Hello, is there a config that allow me to disable the admin user interface Hello, is there a config that allow the user to disable the admin user interface Mar 10, 2025
@Nomia
Copy link
Author

Nomia commented Mar 12, 2025

I've read all the configuration in this section, and the admin configuration section, there seems isn't a setting that will meet the above requirement(disabled the admin ui), could you help give some guidance here, our project is going to be live next week, really appreciate! @tillrohrmann @slinkydeveloper

Image

Image

@pcholakov
Copy link
Contributor

pcholakov commented Mar 12, 2025

Hey @Nomia! The UI itself doesn't expose any additional capabilities that the admin API offers. Also consider that you (or your operations team) will still need access to the admin API in order to deploy services, query/cancel invocations etc. The restate CLI operates over this port/API, as do other deployment automation tools.

What you may consider to tighten up the security is apply IP-based access control, or bind the admin listener to 127.0.0.1:9070 to make it accessible only from the local machine. You can optionally set up an authenticating reverse-proxy in front of it. Would any of these options meet your requirements?

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

2 participants