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

Alternative https port for admin API/UI #47

Closed
harf18 opened this issue Feb 7, 2018 · 4 comments
Closed

Alternative https port for admin API/UI #47

harf18 opened this issue Feb 7, 2018 · 4 comments
Assignees
Labels
Milestone

Comments

@harf18
Copy link

harf18 commented Feb 7, 2018

Proposal

Can you consider adding an option to choose a different https port for the admin API & UI ?

Benefit

We will be able to bloc traffic from internet on this port with a firewall and open it only for internals IPs and enforce the security.

@mathieuancelin
Copy link
Member

Hi @harf18

it would be a great feature and at first I wanted to do it this way but it's not compatible with the deployment model of Clever-Cloud I decided to do it the way it's done right now.

However maybe we can do something here. One solution could be to have a flag to enable/disabled the rendering and the exposition of admin related stuff for the Otoroshi instance facing public access and deploying another Otoroshi instance in your internal network that connect to the same datastore.

Also, in a near future, Otoroshi will have a master / workers mode (#8) that could fix this issue.

@harf18
Copy link
Author

harf18 commented Feb 7, 2018

Thanks @mathieuancelin
Your proposition with flag & 2 Otoroshi instances looks perfect and more flexible than 2 ports !

@mathieuancelin
Copy link
Member

I've created issue #49 for the new feature and I'm closing this one.

Thanks for the report :)

@mathieuancelin
Copy link
Member

app.backoffice.exposed and app.adminapi.exposed has been added to Otoroshi v1.0.2 config. file to expose or not the admin api and admin dashboard

@mathieuancelin mathieuancelin self-assigned this Mar 7, 2018
@mathieuancelin mathieuancelin added this to the v1.0.2 milestone Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants