2 different keys for reading/writing

[Conobi]

Hello,
An idea would be to have two differents keys: one to do GET requests, that can be only used to read data, and another private key that let us to write data on our store.
Thanks !

[bluzi]

Hey @Donokami,

While I see the point of what you're suggesting, I only see little benefits coming out of implementing this.

Right now, jsonstore is meant to be used only in the server, so that the token remains secret and no one can read or modify the data attached to it.
Now, say we apply your idea, developers will be able to use either the read or the write key in the client, but honestly, sharing the write key is super dangerous and should not be done, and I can't think of many applications that will only store public data, and even if they do, I wouldn't recommend sharing the read key.

However, I'd be happy if you could change my mind :)

[knrdl]

This kind of role / view implementation would allow to build a secure website which displays data (for example temperature measurement) by accessing your webservice directly (using the read-key).
The sensor in the backend on the other hand would use the write-key.

I think that's a really nice feature

[bluzi]

Well, I'm willing to give it a shot, if someone will try to implement it as an advanced option, leaving the current behavior as the default behavior, I'll be happy to merge it.