-
Notifications
You must be signed in to change notification settings - Fork 624
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
Incomplete social login for Twitter results in 404 #1707
Comments
Adding ready issues to the Dec V1 milestone. |
@BillWagner I'll take a look at this |
FYI for anyone trying to setup twitter auth for testing, you need to provide a url for callback in the twitter even though its not a mandatory field. Without this you'll run into a 401 error before you even see the consent screen |
@stevejgordon I can't seem to reproduce this exactly as you've described. If I cancel or navigate away from the twitter consent screen and then return to AllReady login screen and try Twitter again it works as expected. However if/when I press the cancel button it gives me an option to return back to AllReady page, that currently fails. I have a potential solution for this |
There a couple of fixes involved here, the original issue actually occurred after user has given consent in social medial login screen and is returned back to the externallogin callback to complete registration. Cancelling here does indeed cause an issue, it appears to be linked to the issue described here aspnet/Identity#915 (comment) |
* Failed twitter authentication (e.g. user cancelling consent) no longer crashes * Partial login with social provider where user navigates away before completing additional information form no longer leaves the login process in an invalid state * All social logins now handle remote failure by redirecting users back to login page * Fixes unit test issues
If you don't fully complete the social login registration (test with Twitter but may affect other services) it's possible to get into a position where you cannot use that provider any longer.
Steps to reproduce:
The local solution is to delete the cookies for the site which removes the Identity.External cookie and allows you to retry the process.
The flow of the site may need review to see if we can prevent this situation.
The text was updated successfully, but these errors were encountered: