XF 1.4 Twitter Error (Authorized token from Service Provider does not match supplied Request Token details)


Well-known member
I am getting the following error for only one user, I tested twitter integration and integrated my twitter account on my own profile and it works fine - but this particular user keeps generating this in error log.

Anything wrong from my end? Or is it from the users end? Almost had 20-25 errors from just one user. But when I tried, the integration test passes and I can also integrate my account.

I have removed the tokens from the error below as I don't know how sensitive it is, but I can provide them if required.

[B]Error Info[/B]
Zend_Oauth_Exception: Authorized token from Service Provider does not match supplied Request Token details - library/Zend/Oauth/Consumer.php:215
Generated By: USERNAME Today at 8:19 PM

[B]Stack Trace[/B]
#0 /home/123456/public_html/library/XenForo/ControllerPublic/Register.php(805): Zend_Oauth_Consumer->getAccessToken(Array, Object(Zend_Oauth_Token_Request))
#1 /home/123456/public_html/library/XenForo/FrontController.php(347): XenForo_ControllerPublic_Register->actionTwitter()
#2 /home/123456/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#3 /home/123456/public_html/index.php(13): XenForo_FrontController->run()
#4 {main}

[B]Request State[/B]
array(3) {
["url"] => string(142) "http://orojackson.com/register/twitter?assoc=6392&oauth_token=ksklIid3Q0qwD9EN2PNNdKTtyZXFKu6J&oauth_verifier=Lx4MXic3We4OoCntDXa82xWxluP6PD0Q"
["_GET"] => array(3) {
["assoc"] => string(4) "6392"
["oauth_token"] => string(32) "tokenremovedfrompost"
["oauth_verifier"] => string(32) "tokenremovedfrompost"
["_POST"] => array(0) {


XenForo developer
Staff member
I'd have to guess it's from the user's end, but this isn't an error I've seen before. Did all the errors happen in a quick succession? The only thing I could guess is that something changed with their session on your site between clicking the Twitter button and coming back to the site.

In general, it shouldn't be anything to worry about, though I wish I knew specifically what happened.