-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AuthContext should handle Authentication Error Response #549
Comments
I absolutely agree! Maybe you wanna contribute to that? We have talked about improving the functionality of |
@mancioshell what do you think about incorporating the way @pamapa mentioned, where we use Regardless of what you end up doing, thank you so much for contributing! 🙏 |
Is there any possibility, that you will solve this issue and add some error handling? |
Hi @marlena-sliwinska 👋 I don't think anyone is working on this, so feel free to contribute! You can join our Discord server (or post questions here) if you want help with anything in that regard. https://discord.gg/SXMpgmPq5F |
@simenandre Unfortunately, when I install the npm package, there is no the onSignInError prop. |
This has been fixed now! |
If any error occurs in Authentication Response, AuthContext skip hasCodeInUrl and enters in a loop calling userManager.signinRedirect() every time.
Maybe hasCodeInUrl should be parse error parameter as specified in the Authentication Error Response specification.
The text was updated successfully, but these errors were encountered: