• r

    rp

    6 months ago
    A refresh token tree is maintained on the backend, but you still need to synchronise the frontend to do only one refresh at a time. Otherwise you can get a false positive of token theft.
  • kurzhai

    kurzhai

    6 months ago
    Ah got it
  • kurzhai

    kurzhai

    6 months ago
    Another (unrelated) question. Are there any plans to make it possible to deploy using DynamoDB database? From what I gather there is no particular need for relational constraints in this project?
  • r

    rp

    6 months ago
    We do require transactions and row level locking. Though there can be a way to do other forms of locks which would work with DynamoDB. We will probably support it after 1yr+ at a minimum.
  • kurzhai

    kurzhai

    6 months ago
    Got it
  • kurzhai

    kurzhai

    6 months ago
    Thank you for your time
  • Tajin

    Tajin

    6 months ago
    Hello, I'm actually developing a website with someone, we are using a postgresql database instance on heroku. So in order for implemeting the auth using supertokens we have to deploy it on heroku using the docker container , right?
  • r

    rp

    6 months ago
    Correct @User . That being said, there is a known issue with our docker containers on heroku: https://github.com/supertokens/supertokens-core/issues/354 The fix for it is also mentioned in the same issue in case you run into the problem
  • r

    rp

    6 months ago
    It's for mysql compatible docker, but same issue applies to our postgresql compatible docker image as well.
  • Tajin

    Tajin

    6 months ago
    alright, thank you!