The temporary credentials need to be store while the user goes to twitter.com and authenticates. Sessions are awesome for this so I use it. You can use other mechanisms if you want.
Abraham ------------- Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sat, Jul 24, 2010 at 09:12, Paul S Gutches <p...@taosinteractive.com>wrote: > > > I follow that. > > I was wondering if the creds needed to be in a session var or not. > > I'll give it a try! > > Thank you! > > > On Jul 23, 2010, at 11:00 PM, Abraham Williams wrote: > > Hello Paul, > > In redirect.php the request token (also called temporary credentials) are > one use. After the user returns from twitter.com having authorized the > application they are exchanged for an access token from Twitter which is > long lasting and what you are after. > > If the request token is not being saved/retrieved from sessions properly > you can print it and the authenticate URL in redirect.php instead of > automatically redirecting. Copy/paste the authenticate url into a browser > window and authorize the app to access the user account. Then you can > manually put the request token into the quick and dirty code instead of > pulling from a session. Keep in mind that you can only use the request token > once so if you don't print the access token the first time you will have to > do it all again. > > Abraham > ------------- > Abraham Williams | Hacker Advocate | http://abrah.am > @abraham | http://projects.abrah.am | http://blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private. > > >
