Firestore works with Firebase auth really well - can just set `/users/uid/k = v` and set a rule only allowing read/write to that uid. Then clientside you could use an auth token generated serverside
firebase.google.com/docs/aut…
1
We're using firebase cloud functions (basically same as AWS lambda) for this - we just deploy the json file alongside the JS. I think if it's running on google cloud then don't even need the file: firebase.google.com/docs/aut…
1
Yep! Couldn't run clientside, but runs on something like cloud functions since they have local read-only fs. (You don't need a VM or EC2 instance) cloud.google.com/functions/d…
2
There are a few examples of using a 3rd party auth provider with firebase here - e.g. Instagram: github.com/firebase/function…
1
I need my app to be the auth service, not a third party auth provider. I am using a piece of data from authenticating MYSELF on another application (not a part of oauth)
1
tbh it sounds like the simplest thing is to have each app generate its own long random string and use that as basically the key for writing and reading data. And this coming from someone who is clearly a fan of OAuth.
Jan 30, 2019 · 4:18 AM UTC
1
1


