#1

This seems to happen intermittently to some users – they will be attempting to connect Twitter with our application but instead of being redirected to our site after logging in, they will be redirected to their twitter.com feed.

Most of our authentication requests go through as expected, but there seems to be a minority who are stuck in a situation where they can never get redirected to our app.

What causes this, and what can we do about it as developers?

#2

In my application, the same thing happens to me, but I think I’ve discovered the “problem”,
1st A user logging correctly in the application
2nd Exit the application
3rd Try again to logging in to the application, but enter the password incorrectly

Instead of redirect to the callback page, twitter redirect to twitter account when log was correctly.

I don`t know why, it seems that twitter decides this.

#3

We have had multiple users report the same behavior this week. One user provided us screenshots:

Sure – first screen shows twitter not connected – only linkedin:
image

So I click on add account and this is what I get:
image

Then I click on Authorize App and it takes me to my twitter account?:
image

We reviewed logs and spent some time doing exploratory testing, but could not replicate the behavior.

#4

Can you please answer the following questions to help us better understand what is going on here?

Which Twitter developer app are you having users authenticate/authorize?
What is your callback URL set to for this Twitter developer app, and what callback URL are you passing through with the POST oauth/request_token endpoint?
Are you using the GET oauth/authenticate or GET oauth/authorize endpoint?
Are you passing along any any optional parameters with any of the 3-legged oAuth endpoints, such as x_auth_access_type with POST oauth/request_token or force_login with GET oauth/authenticate or GET oauth/authorize?
Are the users already signed in to Twitter when they are trying to authorize/authenticate your app?
Are the users experiencing this behavior even when they enter correct credentials, or is it just when they enter incorrect credentials?

Your answers to this question will greatly help us investigate.

Thanks!

#6

@LeBraat I opened a case with Twitter Dev Support and provided these answers there. The case reference is: [ ref:_00DA0K0A8._5004A1kZZ9P:ref ]

#7

Thanks Jason. Did you get a separate number related to your case at all, Something like an 8 or 9 digit id number?

#8

@LeBraat Yes: 0123500498 (from: “Re: Case# 0123500498: Re: OAuth Not Redirecting Back to Our Application [ref:00DA0000000K0A8.5004A00001kZZ9P:ref]”)

#9

Thank you @jasonn - We will continue to help you via this support ticket.

#10

@LeBraat Following up on @ushma_hello 's question. How do we open a ticket with Twitter Dev Support so that we can provide you with the information needed to investigate this issue further? Thanks.

#11

We already have the level of detail that we need and are actively working on a fix. I will keep you updated as we hear more from our engineering team.

Thank you!

#12

Hey Daniel,
Just wanted to add that we also started hearing similar complaints since July 23rd. It’s been a handful of users, so we haven’t been able to reproduce the use case.

We mostly use the authenticate endpoint (authorize in some cases)

Thanks

#13

Thank you @Connexinet - This irregularity does seem to be affecting both authenticate and authorize, and requires the inclusion of the force_login parameter.

1 Like
#14

aha force_login! Not all our workflows have it, but you are right those that have it causes the wrong redirect

Thanks for the update!

#15

This has been recorded internally, no ETA for a fix but folks are aware.

1 Like
#16

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