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.

Sign up for GitHub

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

Jump to bottom

FetchApi is not used, so backstage authorization header is not passed to proxy endpoint #6

Open
ElementalWarrior opened this issue Apr 18, 2024 · 1 comment
Open

FetchApi is not used, so backstage authorization header is not passed to proxy endpoint #6

ElementalWarrior opened this issue Apr 18, 2024 · 1 comment

Comments

@ElementalWarrior
Copy link

This means unless you are hosting behind an authenticating proxy, the backstage /api/proxy/circleci endpoint can be used by anyone who can access the endpoint.

This also means that anyone hosting backstage, and blocking access to api endpoints without an Authorization header, cannot use this plugin.
@ElementalWarrior
Copy link
Author

Looks like this was worked on in the dependent plugin, but then never merged: worldturtlemedia/circleci-api#800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ElementalWarrior