I don't believe the consumer token/secret is linked to an ip address. I don't remember supplying it during application registration so twitter doesn't really know my ip anyway. I'm guessing the access tokens are linked to the IP address which they where issued. This would help prevent access token theft. Deleting all your cached access tokens and getting new ones with the new ip might help fix your issue. I'd test this first before flushing your cache.
Josh On Tue, Aug 4, 2009 at 7:11 PM, MECarluen -TwitterGroup <mecarl...@gmail.com > wrote: > > Hello Gurus- quick question, are the Consumer Token and Secret > assigned to a specific Server IP address? > > I am currently switching my servers/hosts to a different IP address, > but with same domain name. It seems like Oauth returns a "Failed to > validate oauth signature and token" when using the same consumer > tokens and secrets on the new IP addy. If this is what is causing my > problem, how do I remedy? > > Thanks for for confirming one way or the other... comments welcome. -- Josh
