Authentication for JS, Kotlin and Swift #13
-
|
Hello, Just curious on how to proceed in these scenarios. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The precise design on how this going to work is still a work in progress but the general gist is that via sharding you'll only allow client users to be able to access and/or write data they have permission to. Therefore they could mess with their own data (just like they could with API calls) but wouldn't be able to access or overwrite data they don't have access to. If you have more sensitive situations than that, you can just keep using the traditional client/server model and handle all of it on the server. |
Beta Was this translation helpful? Give feedback.
The precise design on how this going to work is still a work in progress but the general gist is that via sharding you'll only allow client users to be able to access and/or write data they have permission to. Therefore they could mess with their own data (just like they could with API calls) but wouldn't be able to access or overwrite data they don't have access to.
If you have more sensitive situations than that, you can just keep using the traditional client/server model and handle all of it on the server.