Callback Error Handling

[bmulholland]

Version

v4.9.1

Reproduction link

https://nuxt-auth.herokuapp.com/callback?error=access_denied&error_description=The%20user%20has%20denied%20your%20application%20access.&error_uri=https%3A%2F%2Fdocs.github.com%2Fapps%2Fmanaging-oauth-apps%2Ftroubleshooting-authorization-request-errors%2F%23access-denied&state=mk-asdfasdf

Steps to reproduce

If something goes wrong with OAuth, or the user clicks "cancel" partway through, they are redirected to the callback page and no error mechanism is available. onError isn't thrown, and there's no built-in convenience methods to deal with this. The error is not displayed on the page, and the nuxt error page is not displayed. The code just bails:

auth-module/src/schemes/oauth2.ts

Line 345 in 5772ccb

return

Digging through the code, it does seem that fetchUser is called in this situation, and it would /seem/ like callOnError should be called as a result:

auth-module/src/core/auth.ts

Line 155 in 6ab4c1e

this.callOnError(error, { method: 'fetchUser' })

However, in this case, oauth2 just returns outright, which is not an error to be caught, and so it all falls right through.

The demo app is affected by this bug: https://nuxt-auth.herokuapp.com/callback?error=access_denied&error_description=The%20user%20has%20denied%20your%20application%20access.&error_uri=https%3A%2F%2Fdocs.github.com%2Fapps%2Fmanaging-oauth-apps%2Ftroubleshooting-authorization-request-errors%2F%23access-denied&state=mk-asdfasdf

What is expected ?

I'd expect there to be some way to handle these types of errors. Probably a hook for receiving the error message, and probably a redirect - to home or login page or error page.

What is actually happening?

User sees endless spinner and there's no built-in way to catch it.

Additional comments?

This seems like it should be core functionality? Am I missing something?

_{This bug report is available on Nuxt community (#c706)}

[bmulholland]

Along these lines, if there's a server side error during code challenge verification (e.g. "code_verifier does not match the code_challenge") then I'd like to show that to the user. However, this is even less possible than what I wrote above, since at least with the callback page I could access the page's params in the URL. There's no way to get Auth's response from the server, so there's nothing I can return from my server to the client that will be accessible.

[toniengelhardt]

I have the same problem, I get a 400 from the backend if the email is already registered and it seems like there is no way to intercept this and show an error... Did you find a workaround for this @bmulholland?

[bmulholland]

No workaround; this will require we add error handling to the module. If you have thoughts on what you'd like that to do, and/or how you'd like it to work, that would help as I think about the design. Or feel free to submit a draft PR with some ideas, too :)

[toniengelhardt]

I'm not sure if it is possible with the redirecting etc, but the most elegant solution would certainly be a catch on the login, just like for the 'local' strategy:

this.$auth
    .loginWith('facebook')
    .catch(error => ...)

I found a way to intercept the error btw, but it is in the plugin and not on the page, which limits the reaction quite a lot. But better than nothing for now:

// auth.js plugin
export default function({ app, route, $auth }) {
  if ($auth.error) {
    if (typeof alert !== 'undefined') {
      alert(...)
    }
    // Remove query params to avoid errors when reloading the page and
    // attempting another login action.
    app.router.replace({ path: route.path })
  }
}

[bmulholland]

Nice find, thanks for posting. You're right that the catch won't work because of redirects. I think we'll need an approach conceptually similar to what you have there - a defined error handling function at the configuration/plugin level. This is something I'll need for my own app in the next few months so I'll put some design into it then.

[toniengelhardt]

Thanks so much @bmulholland !

[jkennedy1980]

The $auth.error property is not documented here: https://auth.nuxtjs.org/api/auth/. I tried to use $auth.onError but it was not fired if the code authorize call fails. I was able to use @bmulholland's solution above inside my Vue login component by accessing this.$auth.error and then modifying my UI to show the message.

[tnabil]

Has anyone found any work-arounds for this? I'm particularly interested in handling the case when the callback URL is called with a server error. At the moment, as @bmulholland mentioned, the user gets stuck on the callback page.

[goatfryed-holos]

Also run into this issue. I think, there is a flaw in the setup. As others pointed out, the runtime will call callOnError with the error, but since no error handlers are registered, nothing happens.
My expectation would be, that plugins are configured before the auth plugin handles anything.

$auth.error is a possible workaround to get any feedback. If it's an axios error, we can get the url with $auth.error.config.url and the response with $auth.error.response. I guess it's enough to add some useful logic, but it's not quite straight forward and we need to figure out the endpoint and the method for ourself.

[bmulholland]

No, and asking for updates isn't going to make anything happen. Please don't do that.

If you'd like to make progress on this, please write up a proposal of how we should implement it. What's the API? What code would change? Or even a PR with a sample implementation for discussion would be welcomed. That would do much more to get what you want :)

[bmulholland]

Yep, that's right, as stated in the OP