Yep. Saw the message, updated our callback URLs AND people CAN log in with Twitter. HOWEVER, I’m still getting a bunch of error messages from Twitter saying the callback url is not approved.

Oh, and I CAN’T CHANGE THE CALLBACK URL properly. Our callback url is /index.aspx?sec=log&sub=exa&site=twitter. The callback url setting truncates the url at the first ampersand. How can I save the proper url? I’ve done it once with one of our sites, but I don’t know how…

Query params are unnecessary for callback URL whitelisting. On the app settings page you can set https://example.com/index.aspx as the callback url and in your OAuth requests https://example.com/index.aspx?cool=param will work just fine.

Hey. I just want to give everybody a heads up that we should read the documentation in order to understand what’s going on. So I decided to actually read the documentation and there it was. The solution was in the documentation.

So, what I did was, I added a link from my application to the list of “Callback URLs” in my Twitter Application Settings and it worked.

I’m using a npm module Passport.js and there is an option for Twitter Strategy called callbackURL. I have added that URL to the list of Callback URLs in my Twitter Application Settings and it worked immediately.

I’ve read the docs and I, like you, am using Passport.js with node. However I have added the callback url from my twitter strategy to my Twitter Application Settings and yet the problem is persisting. I have added a few versions of the url; I’ve changed the domain to be a localhost and the actual IP but nothing is working. Any ideas?