Yes, on my end it does.
On Thu, Apr 9, 2009 at 12:45 PM, Abraham Williams <4bra...@gmail.com> wrote: > Does the consumer key/secret you are using still match what is on: > https://twitter.com/oauth_clients? > > > On Thu, Apr 9, 2009 at 11:30, Adam <coolbeansdud...@gmail.com> wrote: > >> >> Same here. Moved to go the GET method for requesting. >> >> Certain we are not re-using the same token. >> >> Still having problems ... >> >> On Apr 9, 9:42 am, Jason Korkin <jkor...@gmail.com> wrote: >> > Yeah quite certain we're not re-using the same token. We're using GET >> > request. >> > >> > >> > >> > On Thu, Apr 9, 2009 at 10:30 AM, Mobasoft <mobat...@gmail.com> wrote: >> > >> > > I too noticed some funky stuff this morning, but the authentication >> > > flow worked fine for me. >> > > What I did notice is that the verify_credentials.xml request is now >> > > forcing the use of GET (I had been using POST up until now). >> > >> > > Are you certain that you are not re-using the same AccessToken? If you >> > > are, those should be denied as a new one should be generated for each >> > > new request for authorization. >> > >> > > On Apr 9, 9:15 am, Abraham Williams <4bra...@gmail.com> wrote: >> > > > I just went through the authentication flow >> > > withhttp://twitter.abrah.amand >> > > > it worked fine. >> > >> > > > On Thu, Apr 9, 2009 at 09:11, Adam <coolbeansdud...@gmail.com> >> wrote: >> > >> > > > > I too am having problems with OAuth. >> > >> > > > > All of my keys have been de-authorized and I can't seem to re >> > > > > authenticate as well. >> > >> > > > > On Apr 9, 8:36 am, Jason Korkin <jkor...@gmail.com> wrote: >> > > > > > Woke up this AM and went to check on a few things on our site... >> > > found >> > > > > that >> > > > > > all of the oAuth keys had been de-authorized that we had saved >> in our >> > > > > > database. >> > >> > > > > > When I went to re-authorize, I got this error: >> > >> > > > > > Woah there! >> > > > > > This page is no longer valid. It looks like someone already used >> the >> > > > > token >> > > > > > information you provided. Please return to the site that sent >> you to >> > > this >> > > > > > page and try again … it was probably an honest mistake. >> > >> > > > > > I tried to re-generate the URL for authorization (it changed, I >> > > verified) >> > > > > > and it again gave the same "Woah There" message. >> > >> > > > > > Any ideas? >> > >> > > > > > Jason >> > >> > > > -- >> > > > Abraham Williams | Hacker |http://abrah.am >> > > > @poseurtech |http://the.hackerconundrum.com >> > > > Web608 | Community Evangelist |http://web608.org >> > > > This email is: [ ] blogable [x] ask first [ ] private. >> > > > Sent from Madison, WI, United States >> > >> > -- >> > -- >> > Jason Korkin >> > jkor...@gmail.com (Email) > > > > > -- > Abraham Williams | Hacker | http://abrah.am > @poseurtech | http://the.hackerconundrum.com > Web608 | Community Evangelist | http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, Wisconsin, United States -- -- Jason Korkin jkor...@gmail.com (Email)
