However, if you *want* to force the user to authorize each time,
there's an easy way to do that. Just don't save the tokens when you
get them from Twitter!

On Tue, Feb 2, 2010 at 7:37 AM, lalit goklani <lgokl...@gmail.com> wrote:
> There is no need for second authorization. You need to save oauth token and
> secret
> in your db and use it next time he tries to login. These will be valid
> unless he cancels
> the connection with your application. Read more documentation at
> https://docs.google.com/View?docID=dcf2dzzs_2339fzbfsf4 for TwitterOauth-PHP
> by Abraham Williams
>
> Lalit
> Twitter Facebook Application - http://www.twitsfb.com
> Article Directory - http://www.ezinearticles.biz
> Indian Mutual Funds - http://www.mutualfundsnavindia.com
>
> On Tue, Feb 2, 2010 at 4:01 AM, dzuchara <dzuch...@gmail.com> wrote:
>>
>> Hello!
>>
>> Some info:
>>
>> http://twitter.com/oauth/authorize?oauth_token=Qpc0sU53wTy2Y68DHNZAcuUk6VeGxbojhmMvnZY0uQI
>> "An application would like to connect to your account"
>> "Sponsored Tweets by IZEA, Inc."
>>
>>
>>
>> I'm developing a website which uses Twitter Oauth (PHP).
>>
>> Current behavior is the following:
>>  When it is a _first time_ when user log in into my service, he does
>> Sign up in Twitter and "Allow" the application.
>>  When user logs in in _second time_, then there is NO authorization
>> and NO "Allow".
>> It is OK that user is not asked for authorization, because he is still
>> logged in (COOKIE exists).
>>
>> BUT the problem is that I want to show "Allow" window each time users
>> logs in... How to do it ?
>>
>> This behavior has application mentioned in "Some info"... How can I
>> achieve the same effect in my app?
>
>



-- 
M. Edward (Ed) Borasky
http://borasky-research.net

"I've always regarded nature as the clothing of God." ~Alan Hovhaness

Reply via email to