Adding account from admin user edit fails [#2603024]

Hi,

I've just added OAuth 7.x-3.2 and Twitter 7.x-5.11 to my development (behind an institutional firewall) site.

I managed to add the Oauth consumer key and secret with no problem. In my Twitter app, I have the callback URL as http://test.mydomain.org/twitter/oauth .

When I go to http://test.mydoman.org/user/1/edit/twitter (I know, I probably shouldn't use the user number 1 as my admin...) and click on the "Go to Twitter to add an authenticated account button", it takes me to Twitter (same tab) where I'm already signed in. I click the "Authorize App" button, and quickly see a message from Twitter saying it's redirecting me back to the application.

So far, so good!

But it "redirects me" back to http://test.mydomain.org/?oauth_token=e*********zA&oauth_verifier=jl****... . This is just my home page, and the return does not populate my user/1 with a Twitter account.

I've tried this in different browsers, in case it were that. What am I missing? Does it have to do with being behind a firewall or misunderstanding the callback URL?

Joy Payton

Comments

Comment #1

27 October 2015 at 20:22

pm0kjp created an issue. See original summary.

Comment #2

damienmckenna

TN, USA

commented 28 October 2015 at 09:50

Priority:

Major

» Normal

What do you have set as the callback URL field in the Twitter app settings form? It should be set to the same value as you have set up in the module's settings page (admin/config/services/twitter/settings).

Comment #4

SeeSystem commented 13 November 2015 at 18:35

Hey folks,

I ran into same Problem yesterday. Finally it was fixed by doing the following:

1) On apps.twitter.com, "Sign in with Twitter" was set to yes
2) Further on I generated a new access token on apps.twitter.com
3) Changed values for these tokens in Drupal-Backend under Twitter-Settings
4) Then I added a Oauth consumers under "user/1/oauth/consumer", gave the concumer the same name as Twitteraccount is like and set the callback URL to (THINK THIS DID THE FIX): "/twitter/oauth" . I used a relative path and this makes sense for me because base-URL is set by system.
5) On apps.twitter.com the callback URL of the concerning App is set in the same way to "/twitter/oauth".
6) Then I added the authorized Account in Drupal-Backend and I was redirected to right Callback and the Account was added and assigned.
6) Then I cleared all caches and ran cron in Drupal manually

Boom, the Stream of Tweets comes up again....

This is the way it worked for me and our Stream of Tweets, we do not use this Plugin to publish Tweets, so I can't verify if it works right way too then.

Greetz from Germany...hope we could help

SeeSystem