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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摍 #936

Open
mtrezza opened this issue Sep 4, 2023 · 0 comments
Open

馃摍 #936

mtrezza opened this issue Sep 4, 2023 · 0 comments

Comments

@mtrezza
Copy link
Member

mtrezza commented Sep 4, 2023

Link to section:

In some cases you may want to transform an incoming query, adding an additional limit or increasing the default limit, adding extra includes or restrict the results to a subset of keys. You can do so with the beforeFind trigger.

https://docs.parseplatform.org/cloudcode/guide/#beforefind

What is the issue?

Triggers are suggested to be used to prevent access to data. This should not be recommended as Parse Server provides a dedicated security layer for access restrictions. The docs as they are now encourage unsafe, custom practices for access control instead of using the more elaborate mechanisms of access control that were built for that purpose.

Here is just 1 example: https://stackoverflow.com/questions/73575340/parse-platform-authenticate-a-query-in-a-beforefind-trigger

Can you propose a solution?

Coment should be removed and instead an explicitly warning note should be added to triggers with a link to https://docs.parseplatform.org/parse-server/guide/#security.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant