Supports multi-tenancy, prevents tenants from exceeding their authority #1124
-
|
If the node is deployed in the customer's environment, with each user having an account, how to prevent the leakage of other users' data? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi, River does not have any specific features to address job isolation. It’s a general purpose background job engine meant to be integrated into arbitrary backend Go applications. Ultimately any sort of security isolation is the responsibility of the backend application developer. |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to implement it through rls. |
Beta Was this translation helpful? Give feedback.
-
|
Right, so River has no concept of tenants and no ability to do RLS in the engine. I'm not actually sure what that would buy you if we did, other than in River Pro features that use partitioning on arbitrary keys where you could ensure some level of fairness or prevent individual customers from overwhelming the rest. Within individual jobs you can definitely use customer-specific database connections to leverage RLS for the work your job is doing, but again that's an application concern. Your jobs can do pretty much anything. |
Beta Was this translation helpful? Give feedback.
Hi, River does not have any specific features to address job isolation. It’s a general purpose background job engine meant to be integrated into arbitrary backend Go applications. Ultimately any sort of security isolation is the responsibility of the backend application developer.