Provide state object when handling errors in handleCallback

[alexghr]

Describe the problem you'd like to have solved

I can't access the login state (as generated by getLoginState in the login handler) when handling OAuth errors (e.g. error=access_denied) in the callback handler.

Describe the ideal solution

Ideally the state object that I set in the login handler should be available when the callback handler deals with an OAuth error.

Alternatives and current work-arounds

The Auth0 service returns the state parameter back in the URL (as per spec). I could read this parameter but since my app does not control serializing the state (it's this lib's concern) into the authorization request, I can't make any assumptions about how the state is encoded. FWIW it looks to be a base64 string of the JSON object I'm after.

Additional information, if any

Would be nice to have access to the state we set on login so that I might have a better idea of what the user was trying to achieve before trying to login 😄

[adamjmcgrath]

Thanks for sharing this use case with us @alexghr

I'll prioritise this with the team, I'm not sure when we'll be able to get to it, but I'll update this thread when I have any news.

[alexmalev]

@adamjmcgrath it seems that the additional props are stripped when HandlerError is called,
since it strips down all the useful info before the error is returned to the application

[adamjmcgrath]

Thanks for raising this @alexmalev - this has been fixed in the soon to be released v2 by #782