How to use NextAuth without database (only OAuth part)

[atumas-bananamilk]

Question 💬

We use NextAuth to register / login users.

But now we're building a Facebook / Twitter integration (for people to able to tweet etc).
Since they all use OAuth2.0 why don't we reuse what NextAuth already has - the OAuth2.0 part?
But we don't want to store any of that information into "Account" table (which NextAuth does by default).
We just need access / refresh tokens ("Account" table is pretty limited).

We use Prisma + NextAuth for Social Login, but we want to re-use NextAuth's OAuth2.0 capabilities to get access tokens for our internal integrations.

I found this but no info on it:

Can someone help me?

How to reproduce ☕️

Contributing 🙌🏽

No, I am afraid I cannot help regarding this

[ThangHuuVu]

Hi, so just to be clear, by default NextAuth.js does not use DB if you don't specify an adapter. 🤔

But we don't want to store any of that information into "Account" table (which NextAuth does by default).
We just need access / refresh tokens ("Account" table is pretty limited).

Can you explain a bit more here?

[atumas-bananamilk]

Thanks for replying.
We had to specify an adapter since we use Google for registrations to our platform. Our adapter is Prisma.

Now, we want to reuse NextAuth's OAuth2.0 part for Twitter / Facebook API (why build it ourselves?) because NextAuth gets the access / refresh tokens - exactly what we need to call Twitter / Facebook APIs.

This wouldn't be a problem if every platform user uses a unique Facebook account (I just call signIn('facebook') and info gets stored in "Account" table). Problems appear when I use the same Facebook account with another registered user (from "User" table), it doesn't get stored in "Account" table (some limitation between uniqueness of Account <-> User) - we don't want that.
We also have no control over that limitation.

Currently we avoided the limitation by deleting the automatically added "Account" row and recreating it in our own "SocialProfile" table on every signIn event:

Obviously this isn't the best approach but it works. If we could just re-use the NextAuth's OAuth2.0 part to get tokens WITHOUT storing info in "Account" table (only for Twitter / Facebook) it would be perfect as we only need access / refresh tokens.

[ThangHuuVu]

I believe you could do so by writing your own custom adapter. There's a guide here: https://next-auth.js.org/tutorials/creating-a-database-adapter. I think you could return nothing in linkAccount and it'll work 👀
Let me know if this helps!

[atumas-bananamilk]

Thanks, it works the way we implemented but will check linkAccount out!

[kumarabhirup]

@atumas-bananamilk did returning nothing in linkAccount work for you?

[atumas-bananamilk]

1 year later, we now have to add more providers and face the same problem.
We use Prisma adapter (https://next-auth.js.org/v3/adapters/prisma).
Is there a way to adapt it so we can define our own linkAccount within PrismaAdapter?