• r

    rp

    2 years ago
    oh no. We will not be able to see anything from your end. Your sessions will be only stored in your Postgresql db.
  • Sun Walker

    Sun Walker

    2 years ago
    Ahhhhh
  • r

    rp

    2 years ago
    it's a complete on premise solution. You have complete control over it all. haha
  • Sun Walker

    Sun Walker

    2 years ago
    Hahah Oh, And so this cookie thing, does it allow black listing via redis?
  • r

    rp

    2 years ago
    you mean JWT blacklisting?
  • r

    rp

    2 years ago
    via redis
  • Sun Walker

    Sun Walker

    2 years ago
    Is it like this: -> Cookie contains JWT -> Redis Holds Cookie -> Refresh token from token in cookie
  • r

    rp

    2 years ago
    Cookie contains access token (JWT) and refresh token (non-JWT). Right now, we store the refresh token in postgres. We are building out caching functionality using redis and memcached that will then store session data to improve read speeds. But with JWTs, most session verification calls will not need any network operation anyways. So it's super fast!
  • r

    rp

    2 years ago
    Also, what on our site lead you to think "sign up and super tokens will store the db for you" - if you could please send a screenshot, then we can make the messaging there clearer 🙂
  • Sun Walker

    Sun Walker

    2 years ago
    @User I think the wording here could be changed