• r

    rp

    1 year ago
    yes.
  • repomaa

    repomaa

    1 year ago
    ok i think i can live with that
  • r

    rp

    1 year ago
    you can implement blacklisting caching yourself by:- Switching off blacklisting from supertokens' side (which is the default) - Post session verification, check your cache for that session ID (we call this
    sessionHandle
    ). If your cache (blacklist) as this, then disallow the API call by returning a 401.- When calling sign out, or revoking the session some other way, add the session handle to your blacklist
  • repomaa

    repomaa

    1 year ago
    yeah, makes sense
  • r

    rp

    1 year ago
    If you do not switch on blacklisting, and don't implement it by yourself, we recommend keeping the access token's lifetime as short as you possible. To change it, see: https://supertokens.io/docs/session/common-customizations/sessions/change-session-timeout
  • repomaa

    repomaa

    1 year ago
    yup
  • repomaa

    repomaa

    1 year ago
    ok thanks!
  • sycured

    sycured

    1 year ago
    @rp thank you but it's not good for me, excepted session because we're full python and maybe rust, nothing about nodejs for the backend
  • ?

    user

    1 year ago
    is there any vue/nuxtjs samples around ?
  • r

    rp

    1 year ago
    Hey @User we don’t support vue for login yet, but we do support it for sessions.