• Using 3 legs steps with OAuth 1.0
  • After obtain the request token, opening mobile web browser for user
  • https://api.twitter.com/oauth/authenticate?oauth_token=abctoken
  • Authorize [App name] to access your account shown
  • Correct Credentials provided all good!
  • Wrong Credentials provided Super bad user redirected to json.json page (see screenshot)

Is there a better way to handle this flow? any missing params to the auth page?

Thank you!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.