Credentials provider doesn't provide jwt account, jwt profile, session user

[zZHorizonZz]

Since my issue got closed I can't provide a reproducer. I'm posting it here.

Provider type
Credentials

Environment
System:
OS: Windows 10 10.0.23575
CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
Memory: 3.87 GB / 31.63 GB
Binaries:
Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 9.4.2 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.6.2 - ~\AppData\Local\pnpm\pnpm.EXE
Browsers:
Edge: Spartan (44.23575.1001.0), Chromium (119.0.2151.44)
Internet Explorer: 11.0.23575.1001

npmPackages:
next: ^13.5.4 => 13.5.4
next-auth: ^4.24.4 => 4.24.4
react: ^18.2.0 => 18.2.0

npx envinfo --npmPackages "@auth/*" returns nothing

Reproduction URL
This issue can't be reproduced that easilly see decribe section bellow.

Describe the issue
The problem here is that we are trying to use credentials for our in-house provider, but even though login is successful, the refresh token seems like it's working as well and checking if a session is valid for example via useSession works when we are trying to access account or profile in jwt or user (which we don't need it's just it doesn't return anything as well) all are returning undefined for profile in jwt and user in session callbacks it doesn't matter but problem here is that account is undefined so we are not able to retrieve access token.

Code used:

import NextAuth from "next-auth";
import Credentials from "next-auth/providers/credentials";
import {env} from "../../../../env.mjs";

// eslint-disable-next-line new-cap
const handler = NextAuth({
  providers: [
    // eslint-disable-next-line new-cap
    Credentials({
      id: "test",
      name: "test",
      credentials: {
        username: {label: "Username", type: "text"},
        password: {label: "Password", type: "password"},
      },
      authorize: async (credentials) => {
        const res = await fetch(`${env.NEXT_PUBLIC_API_URL}/token`, {
          method: "POST",
          headers: {
            "Content-Type": "application/x-www-form-urlencoded",
          },
          body: new URLSearchParams({
            grant_type: "password",
            username: credentials?.username || "",
            password: credentials?.password || "",
            client_id: "test",
            client_secret: `${env.NEXT_PUBLIC_SECRET}`,
          }),
        });

        const user = await res.json();

        if (user && user.access_token) {
          return {
            id: user.userName,
            name: user.userName,
            accessToken: user.access_token,
            refreshToken: user.refresh_token,
          };
        } else {
          return null;
        }
      },
    }),
  ],
  callbacks: {
    async jwt({token, account, profile}) {
      console.log("JWT token: ", token);
      console.log("JWT account: ", account); //Returns undefined
      console.log("JWT profile: ", profile); //Returns undefined
      if (account) {
        token.accessToken = account.access_token;
      }
      return token;
    },
    async session({session, token, user}) {
      console.log("Sessions session: ", session);
      console.log("Sessions token: ", token);
      console.log("Sessions user: ", user); //Returns undefined

      // Send properties to the client, like an access_token from a provider.
      if (token) {
        session.accessToken = token.accessToken;
      }

      return session;
    },
  },
  events: {
    async signIn(message) {
      console.log("signIn message: ", message);
    },
    async signOut(message) {
      console.log("signOut message: ", message);
    },
    async createUser(message) {
      console.log("createUser message: ", message);
    },
    async linkAccount(message) {
      console.log("linkAccount message: ", message);
    },
    async session(message) {
      console.log("session message: ", message);
    },
  },
  debug: true,
});

export {handler as GET, handler as POST};

Also token response looks something like this:

{
    "access_token": "<token>",
    "token_type": "bearer",
    "expires_in": 28799,
    "refresh_token": "<refresh_token>",
    "as:client_id": "test",
    "userName": "ADMIN",
    ".issued": "Fri, 03 Nov 2023 08:08:50 GMT",
    ".expires": "Fri, 03 Nov 2023 16:08:50 GMT"
}

How to reproduce
This issue can't be reproduced easily see describe section above.

Expected behavior
At least the account should be probably returned so that accessToken can be accessed.

[alpemreelmas]

Any update ?