Replies: 1 comment
-
Did you ever figure this out? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
I currently have a custom NestJS backend that handles authentication using JWTs, with refresh tokens stored in a database and Passport.js for handling authentication. Given this setup, would there be any benefit in integrating Next-Auth into my application?
As far as I understand it, I would still need to create an API endpoint for Next-Auth, and so that would then need to call my NestJS backend. Would this add significant latency compared to making direct calls from the frontend to the NestJS backend? And even if so, would there still be benefits associated with still going with Next-Auth?
Any insights would be greatly appreciated!
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions