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

[FEAT] - Secure resources exposed with the service-proxy #701

Open
2 tasks
IvoGoman opened this issue Nov 6, 2024 · 0 comments
Open
2 tasks

[FEAT] - Secure resources exposed with the service-proxy #701

IvoGoman opened this issue Nov 6, 2024 · 0 comments
Labels

Comments

@IvoGoman
Copy link
Contributor

IvoGoman commented Nov 6, 2024

Priority

(Medium) I'm annoyed but I'll live

User Story

As a Greenhouse Admin I want to restrict access to URLs exposed with the service-proxy, so that the audience of a service can be controlled.

Description

As is everyone who has access to a URL exposed via the service-proxy can access it. In order to avoid misuse of this feature and the exposed service the access should be restricted.

Acceptance Criteria

  • service-proxy URLs should be protected automatically
  • by default all Organization members should have access to the service-proxy URLs

Reference Issues

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Sprint Backlog
Development

No branches or pull requests

1 participant