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

Secure internal-backstage endpoints #561

Open
chriswk opened this issue Oct 15, 2024 · 2 comments
Open

Secure internal-backstage endpoints #561

chriswk opened this issue Oct 15, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@chriswk
Copy link
Member

chriswk commented Oct 15, 2024

Describe the feature request

I would like Edge to hide internal-backstage endpoints by default (except health/ready).

Background

Currently we expose quite a few details in our /internal-backstage urls
/internal-backstage/metrics
/internal-backstage/features
/internal-backstage/tokens
/internal-backstage/metricsbatch

In Unleash's loadbalanced setup, we always block public access to URLs containing /internal-backstage. But not all users of Edge will have our loadbalancer setup.

Solution suggestions

I'd like us to by default not mount the internal-backstage endpoints.

Preferably we'd have a way to setup basic auth for the internal-backstage endpoints, or alternately (for Unleash's sake) a switch turning them all on.

@chriswk chriswk added the enhancement New feature or request label Oct 15, 2024
@chriswk chriswk self-assigned this Oct 15, 2024
@aat2703
Copy link

aat2703 commented Oct 16, 2024

Thanks for opening the issue 👍

@chriswk
Copy link
Member Author

chriswk commented Nov 11, 2024

So, as a work around for now, in 19.6.1 each endpoint has a toggle to turn it off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

2 participants