Admin console and admin login on different port. #389
-
Would it be possible to run the admin console and admin login on a different port? Mainly for security; at least on AWS I could just set a special security group that doesn't allow entering that special port, but would still allow a specific IP to connect to it, or maybe restrict this access to a VPC. As I understand, this would require to run two instances of echo. I think the magic would have to happen in api/base.go but that's as far as my understanding goes. I am not sure how this works with the auto SSL certificates. I think this could be done with an NGINX on front of PB, but that's hardly ideal (as opposed to switching the config on AWS, here I may heve to restart this nginx every time I need the admin console). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
I'm not really sure that I understand the use case for this. Technically you can run the api server and the Admin UI on a different port, but I dont's see any security benefit in doing that.
Why accessing the admin would require restarting NGINX in the first place? NGINX (or any other reverse proxy) is a viable option when you need finer network controls. Could you elaborate a little more on your use case? |
Beta Was this translation helpful? Give feedback.
I'm not really sure that I understand the use case for this. Technically you can run the api server and the Admin UI on a different port, but I dont's see any security benefit in doing that.
Why accessing the admin would require restarting NGINX in the first place? NGINX (or any other reverse proxy) is a viable option when you need finer network controls.
Could you elaborate a little more on your use case?