• r

    rp

    11 months ago
    Using our session recipe for server to server is not recommended cause the "client server" would need to synchronise all calls to the refresh endpoint - which adds complexity to the code + causes issues if the client server's infra is distributed. A simple alternative for this kind of interaction is to use an API key instead.
  • r

    rp

    11 months ago
    This is sort of a complicated topic with several gotchas.. i don't know if my explanation above suffices to answer your question. I am happy to get on a call to explain it 🙂
  • Mydogspies

    Mydogspies

    11 months ago
    @rp Yeah, that makes all sense 👍 Right, in my case I have no need for SSO but machine to machine would be very useful at some point. I will definitely try supertokens for user auth and technically speaking at this point in the project, there is no need to auth the API server. There is nothing sensitive there for now, just pure web content. But planning ahead, the need will come. ^^ Is machine to machine part of your plan in the near future?
  • r

    rp

    11 months ago
    Yea. A LOT of people have asked for machine to machine.. so it surely will be.
  • r

    rp

    11 months ago
    But until we implement it, you can always use another solution, specifically for machine to machine
  • Mydogspies

    Mydogspies

    11 months ago
    I will, but having all in the same shop, so to say, would be soooooo comfy 😌 And thank you so much for your prompt reply!!!! 🙂
  • r

    rp

    11 months ago
    I agree. Using one solution for everything is most convenient.
  • r

    rp

    11 months ago
    Your username is really interesting btw... hahaha
  • Mydogspies

    Mydogspies

    11 months ago
    It's "my dog spies", just to clear any confusion 😅
  • r

    rp

    11 months ago
    oh yea.. got that. I found that funny and interesting