and you need fs to read a json file, so you need a server :/

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…

The firebase-admin sdk requires fs to RUN

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…

There are a few examples of using a 3rd party auth provider with firebase here - e.g. Instagram: github.com/firebase/function…

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)

I feel like if I explained what I'm doing you'd understand why I'm so limited, but I really only need to store a single thing and the simplest solution at this point if mLab doesn't work for it is to write my own service on my own db 😂

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.

Well, I actually need the thing for the k:v pair, it's the one piece of data that is kind of like the key to the whole puzzle box. I'm just being lazy and because it changes every 3 minutes, I can't just grab one and use it for a while. I'm basically writing a small refresh svc

I'm regretting not just standing up a server with a single endpoint at this point lol