You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in goat-guardian, if an error occurs turning the Twitter OAuth login flow, the end-user is shown a bare-bones error page.
It would be great to have an option to redirect the user to the upstream site, so that the upstream site could display an error.
For instance, if the user is going through the Twitter OAuth login flow, after logging in at Twitter, they will be redirected back to goat-guardian with a login token from Twitter.
Goat guardian needs to check for this login token. If it doesn't exist, an error needs to be shown to the user. Currently, Goat Guardian is just showing a very simple HTTP 500 error page, but this could be improved.
Ideally, Goat Guardian would redirect the user back to the upstream site and let the upstream site display the error.
The text was updated successfully, but these errors were encountered:
This is currently only an issue for the Twitter OAuth login flow, but it will probably also be a problem when #1 is implemented for the other OAuth providers.
Currently in goat-guardian, if an error occurs turning the Twitter OAuth login flow, the end-user is shown a bare-bones error page.
It would be great to have an option to redirect the user to the upstream site, so that the upstream site could display an error.
For instance, if the user is going through the Twitter OAuth login flow, after logging in at Twitter, they will be redirected back to goat-guardian with a login token from Twitter.
Goat guardian needs to check for this login token. If it doesn't exist, an error needs to be shown to the user. Currently, Goat Guardian is just showing a very simple HTTP 500 error page, but this could be improved.
Ideally, Goat Guardian would redirect the user back to the upstream site and let the upstream site display the error.
The text was updated successfully, but these errors were encountered: