This behavior resolved as of this morning; no need to investigate further, and no changes made.
On Apr 13, 1:31 pm, Dimebrain <[email protected]> wrote: > Hello, > > Recently, I have noticed that if I attempt to do a request token / > access token exchange, i.e. a new application OAuth workflow, I always > fail with "Failed to validate oauth signature and token" from Twitter > if the application has already been successfully authorized in a > previous workflow. If I revoke the application and try again, it works > fine. > > Now I understand the motive for that, to avoid unnecessary load of > having apps that perform the OAuth exchange on every user session, but > this was not how it was working before. Did I miss an API > announcement? My app persists the token, so for me this isn't the end > of the world. > > First I'd like to know if this is expected behavior. I can faithfully > reproduce the scenario of no access, gain access, try to gain access > again and fail, revoke access and try again to succeed. My expectation > is the OAuth process works even if the user has already granted access > to the user. > > Anyone experiencing this right now?
