-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Allow read-access to protectedFields based on user for custom classes #5887
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
Closed
Dobbias
wants to merge
1
commit into
parse-community:master
from
Dobbias:protected_fields-user-acl-whitelisting
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't you just go through the object ACLs and check if there is a rule with the user id and read true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I understand the
aclGroup
contains all roles associated with the current user and the user id.aclGroup
is not the object's ACL. So I first use theaclGroup
to retrieve the current user's id. Then I use the actual object to check if the user id has read permission usinggetReadAccess
.If there is a better way to retrieve the current user's id (instead of using the acl group) I'll gladly use it.
The
aclGroup
approach is used in theaddPointerPermissions
method too:parse-server/src/Controllers/DatabaseController.js
Lines 1467 to 1482 in ef14ca5
Line 202
avoids the whole retrieval of the user id if there are no protected fields to remove.