When we make requests to oauth/authenticate (when the app is definitely already authorised) we’re getting 302’d to oauth/authorize.
Specifically we’re expecting the behaviour of not having to re-authorize the app as documented here: https://dev.twitter.com/docs/api/1/get/oauth/authenticate
Is this a bug, an issue with the way we’re talking to the API or an issue with our Consumer? (We’ve not changed anything our end).
I wondered if it might be related to this: https://dev.twitter.com/issues/968 ?
Thanks in advance,