Replies: 1 comment 4 replies
-
If I understand correctly, you have two options here. Either create a custom adapter that communicates with your graphql endpoint receiving the User, Account, Session and VerificationRequest data, or you could connect directly with Prisma, and use the official adapter. https://github.com/nextauthjs/adapters/tree/main/packages/prisma/src/index.ts Keep in mind we are in a middle of a major release, the adapter API will be drastically simplified, in case you go with implementing your own. For comparison: https://github.com/nextauthjs/adapters/tree/next/packages/prisma/src/index.ts We don't have full migration docs yet, here is the WIP https://next-auth-git-ndom91-add-migration-docs-nextauthjs.vercel.app/getting-started/upgrade-v4 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We have an existing application with a frontend built on nextjs 11.1, and are trying to implement an email-only login system using next-auth. We can send password reset / registration emails via aws.
The application communicates with a server via apollo client. It does not use any nextjs api routes for this.
The server is running apollo, with prisma as an orm, and type-graphql to resolve the queries.
So far I've read the documentation and ended up at https://next-auth.js.org/adapters/prisma
I'm not sure what to do after reading this.
I have a few questions:
Beta Was this translation helpful? Give feedback.
All reactions