Unable to use 1 Twitter App for multiple subdomains

[1iota]

I have 5 sites running on the same domain, 4 running as subdomains. All 5 urls are properly configured in the Callback URLs list but only the main domain is actually working. Keys are all the same on the configuration side, so I’m at a loss for what is wrong. This app has been working for 5 years, and after the changes last month does no longer.

Is our only option to use an app for every domain? Does anyone know of a workaround that doesn’t completely suck?

[LeBraat]

You should be able to add up to 10 callback URLs per app.

Are you receiving an error message when trying to use the Sign in with Twitter process?
Are you working within apps.twitter.com or developer.twitter.com’s app dashboard?
When you navigate away from the app settings page and back to it, do the callback URLs save properly?

[1iota]

I have the callback URLs listed for each domain, but only one seems to work. When the Twitter sign in window opens on the subdomains it shows an error message indicating the access token is expired, but using the same credentials and code on the base domain doesn’t trigger the error message.

I’ve been using the dashboard on apps.twitter.com. the URLs all persist between different sessions so they do appear to be saved properly.

[LeBraat]

Can you please send me the exact error message that you are receiving?

[1iota]

Whoa there!
The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake.

[andypiper]

Hi there @1iota - that sounds like an error on the actual sign-in dialog rather from the API. Are you using parameters to pass in your subdomain URLs? You should just be able to use https://subdomain.domain.com/targetURI if you have enough space not to need to pass in parameters - and the parameters will be passed on anyway, so if you configured any in the callback URL settings, try removing those.

[1iota]

Hi @andypiper, I updated all our Callback URLs that are not working to match the 1iota.com domain’s settings, and I still get the same behavior. I have listed https://1iota.com/Member/AuthenticateTwitterCallback and https://fallon.1iota.com/Member/AuthenticateTwitterCallback as valid urls, but the functionality still only seems to work when used on https://1iota.com/member/signup but not https://fallon.1iota.com/member/signup.

I assume I’m missing something, but I just can’t tell what it is. This integration was working for 4 plus years until the api changes that were pushed in June.

[1iota]

I have updated the callback urls as suggested, but my subdomains are still experiencing the same issue. Any other options, or do I need to use a different app for every subdomain?

Integration works on https://1iota.com/member/signup, but not https://fallon.1iota.com/member/signup. Callback URLs are entered identically on the developer page for our app just one includes the subdomain.

[LeBraat]

Hello @1iota. I am digging into this now with our product team. I will get back to you shortly.

[LeBraat]

Quick question - The generated oauth_signature with the oauth/request_token endpoint depends partly on the target URL.
Are you sure you are generating this value correctly?

[1iota]

Thank you for your help, the fault was 100% on our end. Your last comment forced me to dig into the bowels of the config transforms and found we were missing an s in the “https” of the target url for these subdomains.

[LeBraat]

I’m glad to hear that you found the issue.

Please let me know if you need anything else!

[LeBraat]