-
Notifications
You must be signed in to change notification settings - Fork 490
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
Enhancements to API structure, whitelist #1886
Comments
@michbarsinai mentioned |
This is the documentation I added that I was talking about above: http://guides.dataverse.org/en/4.7/installation/config.html#blocking-api-endpoints |
If we go about changing APIs from blacklisting to whitelists, it will be easier to reorganize the file structure of API method endpoints. Specifically, there has been discussion around the inclusion of a number of testing API endpoints being in the Admin api class due to ease of blocking on production machines. |
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'. If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment. |
Rather than blaclist APIS, it'd be nice to have the option to white list. That we we can block all and only allow certain ones. Any newly created API, by default would be blocked.
The text was updated successfully, but these errors were encountered: