(no title)
m3h
|
1 year ago
How does an external authorisation service work without the knowledge contained in the application’s database? And vice versa, how does the application make the efficient correct queries from its database when the authorisation information has been externalised?
gneray|1 year ago
Here's a technical post that details these implications in practice: https://www.osohq.com/post/authorization-for-the-rest-of-us
And another post that describes an alternative approach, Oso: https://www.osohq.com/post/local-authorization
(Shocker: I'm cofounder/CEO of Oso)
EgeAytin|1 year ago
Permify provides a Permission Database[0] that unifies the authorization data (as a collection of Access Control Lists - ACLs) in a database of your choice, serving as the single source of truth for all authorization queries and requests via the Permify API.
[0]: https://docs.permify.co/getting-started/sync-data
rzzzt|1 year ago
User "A" comes along and searches for files matching "ragtime". I can ask the permission DB to return the ID of 1499 files "A" has (directly or indirectly) access to, and also run a free-text search to return cca. 195700 files with a title, description or indexed content that matches "ragtime". But what happens next? Can I return an accurate search hit count or filtered result set to the user from his limited access-point of view? Do I need to move metadata into the permission database to do so?