Re:Implementing REST APIs with Embedded Privacy
by andyfang on Monday October 07, 2013 @05:59PM
(#6511583)
We thought about this approach. This would mean that we'd have to have fine-grain permissions logic every time we used that resource. An analogy to this is like having to sanitize literal strings for every user input from a web form; if you forget to sanitize (or in the API case forget to filter the fields) at any point, you have a security bug in your code.
[ Parent
| on HN ]
Re:Implementing REST APIs with Embedded Privacy
by thibauts on Tuesday October 08, 2013 @06:24AM
(#6513938)
You're still doing filtering. The difference I see is your database request code is duplicated. Conceptually the condition is moved but it is bound to exist somewhere. This is IMO a semantics question. Thanks for your input anyway, you gave me a new perspective to wonder.