Back
OAuth exceptions stuck in Appwrite managed redirect page
Hi team, first let me thank you for the amazing project.
I am currently integrating OAuth2 authentication but found out that there are multiple failure cases where users will be stuck in the Appweite managed redirect page (https://<appwrite domian>/v1/account/sessions/oauth2/<provider>/redirect).
One example is when there is an existing user/identity with the same provider email, it will render a 409 User already exists error page. I believe cases like these should be redirected to the failure redirect url and let clients decide how to handle them, instead of having users stuck in an external generic error page.
What do you think about this behavior? I can file a PR if there is no concern.
TL;DR
Issue: OAuth2 exceptions causing users to be stuck in the Appwrite managed redirect page.
Solution: Developers propose redirecting specific failure cases to the `failure` redirect URL for clients to manage, rather than users getting stuck in a generic error page. Developer offers to file a PR if there are no concerns.