07-23-2020, 07:31 PM
(This post was last modified: 07-24-2020, 03:20 PM by mark_talluto.)
Hi Miyaa,
Security is of the utmost importance when working with data in the cloud. Knowing a given recordID is not enough to access your data. The CanelaDB libraries can not be opened in someone else's application because there is an authentication key check unique to your company.
Next, there is the authentication to access data in the cloud (email and password). You would not include those credentials in your shipping application. Each client has their email and password to access a given record. Each user of your app has a unique authentication key.
You never need to store recordIDs in your application. You would get those in real-time via queries or cdb_list() calls.
Your data locally and in the cloud is encrypted. Your data is encrypted with unique values.
RecordIDs are UUIDs. And thus, they are considered to be very unlikely to guess.
https://en.wikipedia.org/wiki/Universall...s%20unique.
Writing logic to determine roles and permissions can be done as Linda provided. But, our ultimate goal is to simplify as many backend tasks as possible. We will eventually release a APIs to help you manage this in the backend. It will make developing apps a lot easier.
We managed to work out many of the details and have a good start on this topic. Alas, we are not done and more work is needed before we can release this feature.
Security is of the utmost importance when working with data in the cloud. Knowing a given recordID is not enough to access your data. The CanelaDB libraries can not be opened in someone else's application because there is an authentication key check unique to your company.
Next, there is the authentication to access data in the cloud (email and password). You would not include those credentials in your shipping application. Each client has their email and password to access a given record. Each user of your app has a unique authentication key.
You never need to store recordIDs in your application. You would get those in real-time via queries or cdb_list() calls.
Your data locally and in the cloud is encrypted. Your data is encrypted with unique values.
RecordIDs are UUIDs. And thus, they are considered to be very unlikely to guess.
https://en.wikipedia.org/wiki/Universall...s%20unique.
Writing logic to determine roles and permissions can be done as Linda provided. But, our ultimate goal is to simplify as many backend tasks as possible. We will eventually release a APIs to help you manage this in the backend. It will make developing apps a lot easier.
We managed to work out many of the details and have a good start on this topic. Alas, we are not done and more work is needed before we can release this feature.