You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I particularly prefer to use a storage-based session token against JWT, but I find a big drawback if my session has to be retrieved from a regular database?
I would want to know if there is a way I could store my session token in a fast access database (like for eg Redis) while storing the rest of the user data in another database (like postgres, or using an ORM adapter like prisma). Is there anything I can do for this using the session callback?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I particularly prefer to use a storage-based session token against JWT, but I find a big drawback if my session has to be retrieved from a regular database?
I would want to know if there is a way I could store my session token in a fast access database (like for eg Redis) while storing the rest of the user data in another database (like postgres, or using an ORM adapter like prisma). Is there anything I can do for this using the session callback?
Beta Was this translation helpful? Give feedback.
All reactions