DynamoDB with email provider results in "Error: Missing or invalid provider account"

[hunternet93]

Adapter type

@auth/dynamodb-adapter

Environment

  System:
    OS: Linux 6.8 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
    CPU: (12) x64 AMD Ryzen 5 3600X 6-Core Processor
    Memory: 13.21 GB / 31.26 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.15.1 - /usr/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 10.9.2 - /usr/bin/npm
    pnpm: 9.12.3 - /usr/bin/pnpm
  Browsers:
    Chrome: 136.0.7103.113
    Chromium: 136.0.7103.92
  npmPackages:
    @auth/dynamodb-adapter: ^2.9.1 => 2.9.1 
    next: 15.3.2 => 15.3.2 
    next-auth: ^5.0.0-beta.28 => 5.0.0-beta.28 
    react: ^19.0.0 => 19.1.0 

Reproduction URL

https://github.com/hunternet93/authjs-dynamodb-provider-test

Describe the issue

When using the DynamoDB adapter in conjunction with the SendGrid provider, I'm getting unexpected behavior and errors when attempting to log in.

The SendGrid provider is able to store a User record in my DynamoDB and send the magic link email. The first time a magic link is opened for a particular email, it appears to work as expected. However, await auth() returns null instead of the session.

On subsequent attempts for the same email, opening a magic link results in the following exception being logged:

[auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
[auth][cause]: Error: Missing or invalid provider account
    at handleLoginOrRegister (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/callback/handle-login.js:24:15)
    at Module.callback (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/callback/index.js:181:142)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async AuthInternal (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/index.js:43:24)
    at async Auth (webpack-internal:///(rsc)/./node_modules/@auth/core/index.js:130:34)
    [remaining lines omitted]

I can see the USER and SESSION records in the next-auth table as expected, but I'm not seeing an ACCOUNT.

How to reproduce

1. Set up the repro app as described in the README.md of the reproduction repo
2. Start with npm run dev and open http://localhost:3000
3. A login form will appear. Enter a valid email address in the input and click the button.
4. SendGrid should send a login email to the address. Once received, click the link.
5. The process will appear to work, but you will not be logged in (await auth() returns null).
6. Try steps 3-5 again with the same email.
7. You'll get an error page, with an exception in the server console.

Expected behavior

Upon opening the magic link, the user should be logged in.

[hunternet93]

This turned out to be a PEBCAK on my part.

When creating the DynamoDB table, I had used the a ProjectionType parameter of KEYS_ONLY on the GSI1 secondary index. (I'm new to DynamoDB and had copy/pasted examples without reading the docs on every property.) This resulted in queries against the secondary index to return only the PK and SK attributes, instead of the full document. Switching to the ProjectionType of ALL fixed the issue and allowed normal login behavior.

For others' reference, here's the working CreateTable call as an aws command:

aws \
 dynamodb create-table \
    --table-name next-auth \
    --attribute-definitions \
        AttributeName=pk,AttributeType=S \
        AttributeName=sk,AttributeType=S \
        AttributeName=GSI1PK,AttributeType=S \
        AttributeName=GSI1SK,AttributeType=S \
    --key-schema AttributeName=pk,KeyType=HASH AttributeName=sk,KeyType=RANGE \
    --table-class STANDARD \
    --provisioned-throughput ReadCapacityUnits=10,WriteCapacityUnits=5 \
    --global-secondary-indexes \
        "[
            {
                \"IndexName\": \"GSI1\",
                \"KeySchema\": [{\"AttributeName\":\"GSI1PK\",\"KeyType\":\"HASH\"},
                                {\"AttributeName\":\"GSI1SK\",\"KeyType\":\"RANGE\"}],
                \"Projection\":{
                    \"ProjectionType\":\"ALL\"
                },
                \"ProvisionedThroughput\": {
                    \"ReadCapacityUnits\": 10,
                    \"WriteCapacityUnits\": 5
                }
            }
        ]"