Instead of using callback-based OAuth, you may want to consider out-of-band
mode OAuth where you prompt the user for a "PIN code" that's provided to the
user instead of a callback.

Twitter's Matt Harris has done a good job detailing how to work with out of
band OAuth:
http://github.com/themattharris/tmhOAuth/blob/master/examples/oob.php

Taylor

On Wed, Oct 13, 2010 at 1:11 AM, abhinav <abhinavshr...@gmail.com> wrote:

> I have integrated twitter in a portal solution. The portal page where
> I register user for twitter, for the OAuth changes I have to give a
> URL for authorization.
> Now my question is that, portlets are not url addressable so how do I
> implement callback functionality for authorization.
>
> --
> 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

Reply via email to