Twitter logout login again bug

Did some more testing and found out that the bug happens in Firefox, but not in Chrome for some reason.

This is a URL for the first succesful login:

https://api.twitter.com/oauth/authorize?oauth_token=LOFO5C1WZQgKjXcDOOm4XeAyhOYejC1BItUYAkUwNk

After logging out and trying another log in, the same token is trying to get used again, but fails since it has already been used:

https://api.twitter.com/oauth/authenticate?oauth_token=LOFO5C1WZQgKjXcDOOm4XeAyhOYejC1BItUYAkUwNk

Clearing the browser cache in FF lets me log in again, but an ordinary user wouldn’t figure that out.

I found out some more about this bug. The used token is not deleted and kept for next login attempt, when it is no longer valid.

The bug is also happening in Chrome browser, I didn’t realize at first.

Another error scenario is when clicking “No, thanks” instead of “Authorize app” in the popup https://api.twitter.com/oauth/authorize?oauth_token=0qhGJ8iLV8…………..

This sends you to https://api.twitter.com/oauth/authorize where you can return to Sign in, and when you do you get the following error in the popup with url https://medborgare.net/index.php?social-connect=twitter-callback&denied=0qhGJ8iLV8………….. :

WordPress > Error – Google Chrome (Title in popup window)

“Login error” (Text in popup body)

I fail to understand why the same token is being used twice in your environment. I tested on my machine and the login works even if I login, logout and then login again. Different tokens are used as expected. Is there a URL where I can see this error happening? Could you test in a WordPress install with the default theme and no other plugin to see if you can reproduce the problem?

Regarding the second problem, I agree that it is not the best user experience and it could be improved (patches welcome). But I don’t see it as error or bug.

Thanks Rodrigo! I tested on another WordPress installation where it looks to be working as it should so it seems you are right. The strange thing though, is that it works fine on Chrome until I trigger another error like the login error I explained above, after that I can’t log back in in Chrome either. Sorry for being so quick to label this as a bug. I will investigate what the culprit is, perhaps something with redirecting the login to the current front-end page since I use the login shortcode in my templates.

Hi Mr Press, I couldn’t reproduce this error on my local environment (tested with Firefox and Chrome) and I couldn’t find the login link on your site.

On my local environment even after canceling the login with Twitter and seeing the “login error” page I was able to login successfully. If you are still having issues please provide the link to your login page where I can check if I’m able to recreate this issue.