CredentialsProvider doesnt seem to work on v4 (beta 7)

[Pruxis]

Question 💬

I have tried both the default sign-in page that is generated automatically or using the signIn function.

Example usage:

signIn('credentials', {
  redirect: false, // tried both with and without redirect.
  email: elements.email.value || '[email protected]',
  password: elements.password.value || 'test',
});

In all cases the following is return from the signIn callback:

{
  user: {
    id: 1,
    name: 'J Smith',
    email: '[email protected]',
    redirect: 'false',
    password: 'fdsfds',
    csrfToken: '92119b7fbbf176b8de47f18ccce385a5caf7c8887bc60d0d793a92f99e55ef1e',
    callbackUrl: 'http://localhost:3000/login',
    json: 'true'
  },
  account: {
    providerAccountId: 1,
    type: 'credentials',
    provider: 'credentials'
  },
  credentials: [Object: null prototype] {
    redirect: 'false',
    email: '[email protected]',
    password: 'fdsfds',
    csrfToken: '92119b7fbbf176b8de47f18ccce385a5caf7c8887bc60d0d793a92f99e55ef1e',
    callbackUrl: 'http://localhost:3000/login',
    json: 'true'
  }
}

How to reproduce ☕️

Provider configuration:

CredentialsProvider({
  name: 'EmailPassword',
  authorize: async (credentials, f) => {
    // const [user] = req.models.user.find({});
    // return user;
    const user = { id: 1, name: 'J Smith', email: '[email protected]', ...credentials };
    return user;
  },
  type: 'credentials',
  credentials: {
    email: { label: 'Email', type: 'text', placeholder: '[email protected]' },
    password: { label: 'Password', type: 'password' },
  },
}),```



### Contributing 🙌🏽

Yes, I am willing to help answer this question in a PR

[Pruxis]

In all of the cases the event signIn is also being called.

   events: {
      signIn: message => console.log('Event:: ', message),
    },

So the cookie will be set accordingly based on https://github.com/nextauthjs/next-auth/blob/main/src/server/routes/callback.js#L414

I don't really see why it's not functioning as expected, upon using useSession in the frontend it always indicates as status unauthenticated.

[balazsorban44]

What's the actual problem here? I can't get it from what said.

Is this a duplicate of #3216?