[auth][error] CredentialsSignin, when return null for CredentialsProvider in the authorize function. #9900
Comments
AmphibianDev
added
bug
AmphibianDev
changed the title
|
Returning |
|
Here is the code solution: Try adding a new case to your switch statement: if (error instanceof AuthError) {
switch (error.type) {
case "CredentialsSignin":
return { msg: "Invalid credentials" , status: "error"};
case "CredentialsSignin":
throw error;
default:
return { msg: "Something went wrong", status: "error" };
}
}This works for me! |
|
great, error resolve @Jay-Karia |
|
@Jay-Karia's fix does not seem to work for me, "[auth][error] CredentialsSignin" logs are still printed to the console even with the additional switch case. Is there really no method to handle invalid credentials in authenticate without throwing an error? |
100% |
Did you win it? |
|
I have win it. But it looks like a crutch. Before use signIn('credentials',{...}) execute checkup on isExisting smt if result will be null we return {error: 'error'} and if we found for example user we got pure data to method signIn. |
|
Why it this closed ? |
|
I do not know about you guys, but I could not find a good way to handle errors in v5, so I switched to v4 instead |
|
I agree with all of you about the error logs, but it solves the errors at frontend in the development server. |
|
This needs to be reopened |
so far, this is the only solution I can do with V5; simply check if the user actually exists or is valid before calling the authorization. It's not the best approach, unlike v4, but there's nothing we can do. |
@balazsorban44 so every time a login fails it will spawn an error on server side? It doesn't sound right to me. We should be able to handle failed login cases without treating it as an error, since it is not an error at all. |
I get it, it's frustrating as well, I am trying to find a good error handling method also but nothing seems to work. We need to understand tho that v5 is still in beta and it's not meant for production. |
Environment
System:
OS: Windows 11 10.0.22631
CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
Memory: 25.36 GB / 47.93 GB
Binaries:
Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (121.0.2277.98)
Internet Explorer: 11.0.22621.1
npmPackages:
@auth/prisma-adapter: ^1.2.1 => 1.2.1
next: 14.1.0 => 14.1.0
next-auth: ^5.0.0-beta.5 => 5.0.0-beta.5
react: ^18 => 18.2.0
Reproduction URL
https://github.com/AmphibianDev/todo-app/tree/main
Describe the issue
The error occurs only when
authorizereturns null, if it's returning a user, it works.How to reproduce
auth.config.ts
auth.ts
Error:
Expected behavior
Rejecting the singin attempt without throwing a server error in the console, and showing the user "Invalid credentials"
The text was updated successfully, but these errors were encountered: