So you're using Sign In With Twitter. Are you sure you're going to the right URL? That is, are you going to /oauth/authorize or /oauth/authenticate? IIRC, if you use the latter, they should only be prompted once. If you use the former, they'll be prompted every time.
On Tue, Oct 27, 2009 at 11:11, CreativeEye <creativv...@gmail.com> wrote: > > I missed this in the 1st message: my app uses Twitter for login > purposes. So there is registration on my app. > How do I use the saved access token? > Yes I am saving the access token. yet i am not able to see where I > will use that. > > -- > On Oct 27, 9:16 pm, JDG <ghil...@gmail.com> wrote: > > are you saving the access token? > > > > On Tue, Oct 27, 2009 at 09:57, CreativeEye <creativv...@gmail.com> > wrote: > > > > > This is first app using OAuth. As far as I have known, once the user > > > has authorized an application, in the subsequent visits, he is not > > > shown the page "Allow/Deny" buttons but automatically redirected to > > > application. > > > > > But in my application, every time the user tries to login, he is > > > greeted with Allow/Deny button. Is there anything extra required to > > > instruct the OAuth server to behave as above? I am using > > >http://twitter.abrah.am/ > > > TwittterOAuth class. > > > > -- > > Internets. Serious business. > -- Internets. Serious business.