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

Allow to restrict access to POST endpoints #670

Open
ThomasJejkal opened this issue Feb 12, 2025 · 1 comment
Open

Allow to restrict access to POST endpoints #670

ThomasJejkal opened this issue Feb 12, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@ThomasJejkal
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, despite of DELETE, all endpoints are secured on a true/false basis, i.e., if someone has accepted credentials, schemas and documents can be created without restriction. In order to be able to restrict the proliferation of arbitrary numbers of schemas (and documents) in a single instance of MetaStore, a more fine-grained restriction also of POST endpoints should be possible.

Describe the solution you'd like
The easiest solution might be to allow to configure access to POST endpoints (POST /api/v2/schemas/ and POST /api/v2/metadata/) via WebSecurityConfig and application.properties There could be for example a configurable role reflected via groupId, which enables the caller to access these endpoints.

Describe alternatives you've considered
For the time being, this could also be covered on the UI level, but access to the API will still be "unrestricted" in that sense.

@ThomasJejkal ThomasJejkal added the enhancement New feature or request label Feb 12, 2025
Copy link
Contributor

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
None yet
Development

No branches or pull requests

2 participants