Hi Dan, Twitter actually doesn't need to be able to access your callback URL -- the web browser executing the callback does though.
On your application record, just use a placeholder for the callback URL field (like your business's public-facing web site). On the request token step of OAuth, dynamically supply an oauth_callback pointing to the URL behind your firewall. Once the user authorizes, they'll be redirected to your URL as long as it's accessible for them. Thanks, Taylor @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer Advocate On Wed, Feb 16, 2011 at 1:34 PM, Dan <dro...@gmail.com> wrote: > Hello, > > I am just getting started developing some proofs-of-concept for my > company. One major snag is that I am of course behind a firewall. The > OAuth API expects a URL that is available to twitter.com. I can't > really do much more unless I start opening some ports (frowned upon). > What solutions have other developers in the same position used? > > I also would like to avoid any user interaction with twitter (should > be completely opaque). From reading the documentation it would appear > that the XAuth is better suited to my use case. What experience have > people had with this? > > Thanks for your time... > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
