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

Enhancements to API structure, whitelist #1886

Closed
scolapasta opened this issue Apr 4, 2015 · 4 comments
Closed

Enhancements to API structure, whitelist #1886

scolapasta opened this issue Apr 4, 2015 · 4 comments
Labels
Feature: API Feature: Installer Feature: Permissions Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured

Comments

@scolapasta
Copy link
Contributor

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.

@scolapasta scolapasta added this to the In Review - 4.0.x milestone Apr 4, 2015
@pdurbin
Copy link
Member

pdurbin commented Jan 26, 2016

@michbarsinai mentioned post-install-api-block.sh at #976 (comment) but the script never made it into to zip distribution of Dataverse (a release). I know this issue is about enhancements but I thought I'd at least mention it here. @landreev has mostly worked on adding this files to the zip. I'm emphasizing the need to run the script as part of #2884.

@pdurbin
Copy link
Member

pdurbin commented Jun 29, 2017

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

@pdurbin pdurbin added User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured Type: Suggestion an idea labels Jul 13, 2017
@matthew-a-dunlap matthew-a-dunlap changed the title Enhancements to API blocker Enhancements to API structure, whitelist Sep 15, 2017
@matthew-a-dunlap
Copy link
Contributor

matthew-a-dunlap commented Sep 15, 2017

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.

@cmbz
Copy link

cmbz commented Aug 20, 2024

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.

@cmbz cmbz closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: API Feature: Installer Feature: Permissions Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured
Projects
None yet
Development

No branches or pull requests

6 participants