Problems with not linked accounts after upgrading from v3 to v4

[chrishornmem]

Hi,

I am experiencing the "OAuthAccountNotLinked" ("To confirm your identity, sign in with the same account you used originally."), error for my users after migrating from v3 to v4.

I am using GoogleProvider.

Seems like all users are affected (on local dev not production :) )

I actually don't know how recover from this error, I've tried deleting the sessions in the db but to no avail.

Do you know if this particular migration scenario has been tested? Any ideas what could be wrong?

I was using mongo database sessions in v3, like this:

  // v3 [...nextauth].js
  database: {
    type: 'mongodb',
    useNewUrlParser: true,
    useUnifiedTopology: true,
    useFindAndModify: false,
    url: process.env.DATABASE_URL,
  }

and now in v4:

// v4[...nextauth].js
{
  adapter: MongoDBAdapter(clientPromise),
  session: {
    strategy: 'database',
    maxAge: 30 * 24 * 60 * 60, 
    updateAge: 24 * 60 * 60,
}

[chrishornmem]

@balazsorban44 I think I found the problem - in v3 the database model for accounts table uses a field named "providerId" whereas in v4 it seems to have been renamed to"provider". That means there is a db migration to do when upgrading from v3 to v4?

[ndom91]

@chrishornmem Thanks for the quick feedback. You're right, with Mongo being a document database, a lot of the migration becomes unnecessary. However after going through it one more time, I see there are actually a few more renames that would seemingly also have to be done in mongo.

For example:

db.getCollection('accounts').updateMany({}, {
  $rename: {
    "provider_id": "provider",
    "provider_account_id": "providerAccountId",
    "user_id": "userId",
    "access_token_expires": "expires_at"
  }
})
db.getCollection('users').updateMany({}, {
  $rename: {
    "email_verified": "emailVerified"
  }
})
db.getCollection('sessions').updateMany({}, {
  $rename: {
    "session_token": "sessionToken",
    "user_id": "userId"
  }
})

What do you think?

[chrishornmem]

@ndom91 Well I just checked on my production system with the following in my package.json

"next-auth": "^3.29.0",

And for me, sessionToken, userId and emailVerified are already named correctly.

Here is the full list on v3:

accounts collection

userId
providerType
providerId  -> beware! must be renamed to `provider` (causes the issue I have mentioned in this ticket) 
providerAccountId
refreshToken
accessToken
accessTokenExpires

sessions collection

expires
sessionToken
accessToken

users collection

email
image
emailVerified

Your suggestion won't cause any issues of course.

[ndom91]

@chrishornmem great, thanks for double checking!

It seems the v3 schema that I went off of (I believe it was the latest one in the docs that I could find for v3), might have been out of date as well.

But as you said, additional renames that aren't here won't hurt. I think I'll leave them in for those that may have not had such an up-to-date schema as you seem to have in v3.

[t4sk]

For GitHub Oauth, I also had to change providerAccountId from number to string

# update github providerAccountId from number to string
db.accounts.updateMany({provider: "github"}, [{$set: {providerAccountId: {$toString: "$providerAccountId"}}}])

[ndom91]

@t4sk thanks for the Mongo snippet. This was already mentioned in the technical "MySQL" and "Postgres" migration docs (https://next-auth.js.org/getting-started/upgrade-v4#database-migration), however was apparenlty missing from the Mongo one. Would be awesome if you could put up a PR 😁