Advanced Permissioning In Middleware
I need to handle somewhat complicated permissioning logic, for example:
Is there a good pattern for applying this sort of logic in middlewares? Currently, I can create a verbose permission set in
The
I don't think I'd want to set that
Any thoughts?
User A can read (but not write) tasks from Facility BUser A can read (but not write) tasks from Facility BIs there a good pattern for applying this sort of logic in middlewares? Currently, I can create a verbose permission set in
ContextContext for that user, but I'm not sure how best to handle a facility-specific route, for example trying to read tasks from Facility Bread tasks from Facility B. The
ContextContext will contain all of that user's permissions, but I'm not sure how to check those permissions against a route-specific ID (for example facilityIDfacilityID) in a middleware. I don't think I'd want to set that
facilityIDfacilityID in context (since a lot of procedures won't have a facilityIDfacilityID at all) and it doesn't look like there's a way to pass dynamic values into middleware using MetaMeta. Any thoughts?
