-
Notifications
You must be signed in to change notification settings - Fork 34
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
Per-entity CRUD filters and authorizers for UpdateBuilder #502
Milestone
Comments
andrus
changed the title
Per-entity update filter
Per-entity create/update/delete filters
Nov 28, 2021
andrus
changed the title
Per-entity create/update/delete filters
Per-entity CRUD filters for update/delete operations
Nov 28, 2021
andrus
changed the title
Per-entity CRUD filters for update/delete operations
Per-entity CRUD filters and authorizers for update/delete operations
Dec 5, 2021
andrus
changed the title
Per-entity CRUD filters and authorizers for update/delete operations
Per-entity CRUD filters and authorizers for UpdateBuilder
Dec 5, 2021
andrus
added a commit
that referenced
this issue
Dec 5, 2021
andrus
added a commit
that referenced
this issue
Dec 5, 2021
.. create/update/delete filters must cause immediate failure of the entire request, not filter operations
andrus
added a commit
that referenced
this issue
Dec 5, 2021
.. renaming create/update/delete filters to "authorizers". The new name is more appropriate as they fail entire requests, not just exclude disallowed operations .. moving from "filter" to "access" package
andrus
added a commit
that referenced
this issue
Dec 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to #501, let's implement a set of rules for CRUD operations (
UpdateBuilder
). This will require a read "filter" and create/update/delete "authorizers".403 Forbidden
should at least one of the checks fail.Usage Example
This is per-request API. Same rules can be applied per Agrest stack using similar AgEntityOverlay methods.
The text was updated successfully, but these errors were encountered: