Twitter Login not working

Kasey_Luft · April 25, 2020, 3:24am

Following up from a Slack conversation with Mark Piller:

What should the callback URL be for the twitter account using the REST API? I am getting the following Twitter error when attempting step 6 of the twitter social login tutorial:

https://backendless.com/docs/rest/mgmt_social_settings.html

This is the error I am getting:

{"code":3022,"message":"Unable to login user due to error: 403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following).\n<?xml version='1.0' encoding='UTF-8'?><errors><error code=\"415\">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>\n","errorData":{}}

Thanks for your help!

mark-piller · April 25, 2020, 3:37am

Hi Kasey,

So that the product team can assist you as quickly as possible, could you please attach a screenshot showing how you configured the app in your Twitter account?

Regards,
Mark

Kasey_Luft · April 25, 2020, 3:57am

As Mark suggested, here is the set up of my twitter account:

Thanks for any help you can provide!

Inna_Shkolnaya · April 25, 2020, 8:57am

Hello @Kasey_Luft

We will definitely update the documentation for setting up Twitter login.
In your Twitter developer account you should add the following links:

Website URL:

https://api.backendless.com

Callback URL:

Organization website URL:

https://api.backendless.com/YOUR-APP-ID/API-KEY/users/social/twitter/authorize

Also remember to add the consumer API keys: https://monosnap.com/direct/mqS5B6YoiPGX4RbZjtAFXZH0iipX4G

Regards,
Inna

Kasey_Luft · April 25, 2020, 10:18pm

@Inna_Shkolnaya Thanks I was able to get to the authorization page! However, when I clicked authorize I got this very long stack trace - is that normal? When I click authorize, what should it do?

Andriy_Konoz · April 27, 2020, 7:22am

Hi @Kasey_Luft!
It seems like problem with fields mappings. What fields mappings did you used?
We will improve error message for such cases.

Regards, Andriy

Kasey_Luft · April 27, 2020, 12:35pm

@Andriy_Konoz I was using the following fields mappings:

{“data”:{“fieldsMapping”:{“userId”:“twitterUserIdInBackendless”, “screenName”:“twitterScreenNameInBackendless”}, “redirect”:true}}

Andriy_Konoz · April 27, 2020, 4:26pm

@Kasey_Luft you have mistake in your JSON - “fieldsMapping” field must be placed in root of body. “redirect” field must be placed in root also.
I think this may cause your problem.
Correct variant should look in next way:

{
“fieldsMapping”: {
“userId”:“twitterUserIdInBackendless”,
“screenName”:“twitterScreenNameInBackendless”
},
“redirect”:true
}

In tutorial body formed in way that was described by me:
https://backendless.com/docs/rest/mgmt_social_settings.html
Also more about Twitter login you can find by this link:
https://backendless.com/docs/rest/users_login_with_twitter.html

Please, try to use mappings suggested by me and write back about results.

Regards, Andriy

Kasey_Luft · April 27, 2020, 6:18pm

@Andriy_Konoz Looks like that was it.

I had changed it before when I couldn’t get the API to work but after I made the first set of changes I hadn’t updated the mapping. This fixes that now! Although, using postman, it appears the redirect is in French. Is that supposed to be that way? Haven’t tested it out in my website yet. This seems to have solved my solution though, thanks!

Andriy_Konoz · April 28, 2020, 6:29am

@Kasey_Luft, about Twitter auth page language.
You can try to change its locale by providing different value in header " Accept-Language". This header is generated and sent automatically by browser for each request. It means that each user will get Twitter auth page in different locale that was choosen from one of the locales provided by that header.

More information about this header you can find by this link:

Regards, Andriy

Kasey_Luft · April 29, 2020, 10:04pm

@Andriy_Konoz @Inna_Shkolnaya

Another question. I was able to get the twitter account working with Postman, but when I am using the API call in my website I get the following error:

Would either of you happen to know what this means? I was under the impression I could just create an API request and it would run in my web app using PHP. Is there an extra step I need to do?

Does the backendless api automatically authorize the Twitter api, or is this a separate step I need to do on my own before calling this api?

Thanks!

Andriy_Konoz · April 30, 2020, 6:25am

@Kasey_Luft
Backend API automatically autorize Twitter user if for authorization was used URL generated by
http://api.backendless.com/v1/users/social/oauth/twitter/request_url
Your error indicate that something went wrong in your code since you got infinite redirect loop, which was terminated after reaching limit of redirects.

Actual workflow of autorization is next:

You request autorization URL for Twitter.
You redirect user by received URL.
User authorize himself on the Twitter side.
Twitter send you in response HTTP code for redirection to callback URL that was specified in authorization URL. Redirect URL must be present in header “Location” of response.
You call redirect URL which points to Backendless.
Backendless perform authorization of user and return you user data along with user auth token.

I supose that your code made wrong redirect at step 4. Check if you properly read value of “Location” header.

Regards, Andriy

Kasey_Luft · April 30, 2020, 1:18pm

@Andriy_Konoz Thanks for the detailed explanation, looking back I can’t actually see the ‘Location’ header in any of my calls.

I went back to https://backendless.com/docs/rest/mgmt_social_settings.html and realized I could never get step 6, 7, 8 to work.

When attempting to run step 6 with the following URL http://api.backendless.com/v1/users/social/oauth/twitter/request_url I got this error using the backendless app id and rest secret id

{
    "code": 2002,
    "message": "Version is disabled or provided wrong application info (application id or secret key)"
}

It was then suggested to me to try the URL found in this link here https://backendless.com/docs/rest/users_login_with_twitter.html (https://api.backendless.com/application-id/REST-api-key/users/social/oauth/twitter/request_url).

So I’m wondering if maybe I never authorized it properly in the first place and that’s why I see what I’m seeing? Or should that not be a factor?

Andriy_Konoz · April 30, 2020, 1:36pm

@Kasey_Luft
In tutorial for step 6 provided outdated URL. It is ok that you used for obtaining authorization URL route from https://backendless.com/docs/rest/users_login_with_twitter.html
If you succeeded in authorization via Postman and saw JSON with user data from Backendless then there must be no problems in real authorization as long as you stick to same workflow.

What response from API did you get at line 226 in api.php file?

Regards, Andriy

Kasey_Luft · April 30, 2020, 1:55pm

@Andriy_Konoz Ok, thanks!

I am using a tool called Wappler which is a low-code software tool. A lof this stuff has already been created and I just input values. I am able to use the rest API function when connecting to Backendless login no problem but it looks like social auth is a bit tricky. I have attached the full app.php file. I am still learning the ins and outs so I am not entirely sure what all of it means. If anything pops out at you that is wonderful, if not then I will continue to pick away at it.

Thanks again!

Andriy_Konoz · April 30, 2020, 2:00pm

@Kasey_Luft
If REST authentication is working correctly then, most probably, problem caused by generated code.
I recomend you to debug it using XDebug or in some other way.

Regards, Andriy