Return an error message to client in the same page

[natsathorn]

Your question
How to return the message to the login form?

What are you trying to do
I'm using Credentials provider which will just fire a request to another server for login. It's work fine when everything go as plan. In the case that login is not success, I can only send the error message via querystring which make the page reloaded.
Is there any other way to send the errorMessage back to the form without reload it.

FYI. I used signIn('myAuth', { ...data }) on my login form.

Feedback
In this section, it only shows these two options.

// You can also Reject this callback with an Error or with a URL:
return Promise.reject(new Error('error message')) // Redirect to error page
return Promise.reject('/path/to/redirect')        // Redirect to a URL

• Found the documentation helpful
• Found documentation but was incomplete
• Could not find relevant documentation
• Found the example project helpful
• Did not find the example project helpful

[bdub9]

I'm having the same issue. Desired use case to skip a redirect:

1. Check if a user/password combo exists or password match.
2. They don't. Would like to Promise.reject with an error code or error message WITHOUT redirecting. Doesn't seem like there's a way to skip the redirect, even Promise.reject('/login?errorMessage=tryAgain') here (my form is on /login) reloads the page. How can we just send down a simple error message in a response so our client can handle it?

[mdesilva]

I'm having the same issue as well. Would be nice if we can just do the login RESTfully and do the redirection ourselves.

[MateuszWawrzynski]

bump
@iaincollins

I'm looking for the answer for exactly the same problem.
Any ideas?

Is there any way to handle error code on the signin page without redirecting to "error" page and just show the error under the login form?

[mdesilva]

You can return the error as a query parameter to the login page

[flosrn]

I would like to know if is there an other way to send error message to client besides with query params ?
Because query params cause the refresh of entire page and cause flashing who is little bit weird for the client

[balazsorban44]

Hi everyone, I am working on this right now!
Would this PR solve your issue?: #1219

[dovalid]

Yep, looks perfect! Thanks for your work.

[yannicktian]

Thanks @balazsorban44
As @StefanSelfTaught mentioned here, it would be super to have the option to disable redirect for Email provider as well
#1219 (comment)

[yannicktian]

@balazsorban44 I have a small PR ready but cannot push

ERROR: Permission to nextauthjs/next-auth.git denied to $ME.
fatal: Could not read from remote repository.

Do I have to be added to a specific team or am I missing something 🤔 ?

[StefanSelfTaught]

@yannicktian Did you fork the repo?

[yannicktian]

@StefanSelfTaught I've cloned it
git clone git@github.com:nextauthjs/next-auth.git && cd next-auth

• Pulling is ok, but I can't push

[balazsorban44]

You don't have push access to the repo, only maintainers do.

Check out this tutorial: https://jarv.is/notes/how-to-pull-request-fork-github/

[yannicktian]

@balazsorban44 @StefanSelfTaught Cheers sorry for this extremely noob discussion 😅 I should contribute more often to open source project, here is the PR #1379