Where are you storing the secret upon authorization? Is it going into persistent storage (such as a database) for future use?
Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 11:07 AM, Hameedullah Khan <[email protected]>wrote: > > > > On Apr 13, 11:59 am, Zachary Voase <[email protected]> wrote: > > As far as I know this is not an issue. Users only have to accept the > > first time they use an application; on subsequent authorization > > requests, Twitter will redirect them to your app straight away. > > > > Strange, > > I always get that Accept/Deny Page. I am wondering what I am missing. > > Here is what I am doing: > > 1. request a token from twitter. > 2. Redirect user to authorization url with the token requested in 1 > 3. once the user returns from twitter, get the access token (or > secret) from twitter based on token requested in 1. > 4. use the secret for further api requests to twitter. > > Thanks, > Hameedullah Khan >
