#1027 Restrict Sensntive Data Exposure via API Call #1036
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GET
api/teamAPI shows team information for Democracy Lab members on the page:https://www.democracylab.org/about. The API exposed sensitive volunteer data like application test, joining date, isCoOwner, etc. These fields are not displayed/used on the front-end but are still returned as a part of the API response.This fix creates a new structure called
VolunteerMinimalDetailsAPIDatathat contains only the required information about every volunteer. This new structure is integrated intoProjectDetailsAPIDatastructure.Closes Issue: #1027