GOOGLE SIGN-IN identity column filled with "oAuthId"

User Service
1

Backendless Version (5 or 6? whatever REST API uses)

Client SDK (REST)

Application ID: FF55A111-06AF-7EB1-FFDE-B5B62760CA00

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. REQUEST GOOGLE LOGIN / REGISTER URL WITH REST API…
  2. LOGIN/REGISTER WITH GOOGLE
  3. REDIRECT TO A BACKENDLESS CONFIRMATION PAGE or ( like how the email verify page can be edit )

Actual Behavior

GOES TO THE ADDRESS:
https://api.backendless.com/FF55A111-06AF-7EB1-FFDE-B5B62760CA00/82EF8043-6A25-48C9-8025-B66AC81A019C/users/social/googleplus/authorize?state=8a05cf3a-d35a-4f79-b79e-fae032f4fda9&code=4%2F0AX4XfWjX5sxl8X2eyAbP_b8dS_P_bToqZp0VqjD9_jaagr-QlGjBwmFaXZ5eZFTvCSeS8A&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+openid&authuser=3&prompt=none#

THE PAGE IS JUST WHITE WITH TEXT, SHOWS THE FOLLOWING INFO:

{"character_data":null,"lastLogin":1626567995744,"userStatus":"ENABLED","displayName":"106052425464341490309","init_user_upon_login":true,"ownerId":"F354726B-C9EE-4149-A7D0-748318244671","gem":0,"nickname":null,"golden":0,"___class":"Users","blUserLocale":"en","prevTimestamp":0,"objectId":"F354726B-C9EE-4149-A7D0-748318244671","email":"organization13.ka@gmail.com","prevTimestamp_NFT":0,"created":1626567995000,"accountType":"OAUTH","avatar":null,"socialAccount":"OAUTH","oAuthIdentities":[{"oAuthId": "106052425464341490309", "displayName": "JES OC", "providerCode": "googleplus"}],"user-registered":true,"WAXaddress":null,"ETHaddress":null,"user-token":"A536BFC3-F68E-4C8C-918C-657494AB9A98","updated":1626567995000,"hash":"ead553533c16a3401a3a60a90d56f66005a5b44d"}

EXTRA INFO:

  1. displayName is my identity column… ( But it puts the “oAuthId” value in there for some reason? )
  2. On a related note, I’m having a password auto-length? error with logins, I create sha512-HMAC strings of passwords before put in database…

PLEASE HELP!

2

Hi @JesterOC !

Expected Behavior
Please describe the expected behavior of the issue, starting from the first action.

  1. REQUEST GOOGLE LOGIN / REGISTER URL WITH REST API…
  2. LOGIN/REGISTER WITH GOOGLE
  3. REDIRECT TO A BACKENDLESS CONFIRMATION PAGE or ( like how the email verify page can be edit )

Current behavior is expected behavior for REST APi key. To achieve your desired behavior you should control user authorization flow and perform redirect by yourself when authorization succeeded. I would advice you to open OAuth authorization page in separate frame and at the end to redirect user to desired page.

  1. displayName is my identity column… ( But it puts the “oAuthId” value in there for some reason? )

We are sorry that you have encountered this problem. It was caused by changes on the server side. Last year we have added support for multiple login providers per user. Due to this change we have moved provider specific columns to separate element in oAuthIdentities JSON field. To restore your original behavior you should set this value manually to that column in afterOAuthRegister event handler.

  1. On a related note, I’m having a password auto-length? error with logins, I create sha512-HMAC strings of passwords before put in database…

I have fixed this problem. Could you please try and confirm that problem gone?

Regards, Andriy

3

No the problem persists, though now i’m unsure it’s a password length issue as it no longer gives the same error:

**ERROR: **
Unable to complete operation. Backend application is not properly configured. Contact the application developer and report a problem with Email Configuration.

So now it appears it’s the email??.. the pw hmac is not over the 500 character limit set

and Here’s my server’s debug log:
DEBUG: found TCPmessage, looking for msg_id…
DEBUG: msg_id = Account Register
DEBUG: message = {‘msg_id’: ‘Account Register’, ‘pw’: ‘0dbfa1fa8723b54e721b873d668af8014a89cf7d3ce91d65e3fb7e0199254cb84443f58e49b1984f8c833aee0bf4af6494b699bb121d7226a2aa62a9bdc28bf7’, ‘username’: ‘Admin’, ‘email’: ‘jesteroc.games@gmail.com’}

4

It looks like there is a problem with your SMTP server configuration. Please, check it and try again to register user.

Regards, Andriy

5

I couldn’t see a problem, so i just created a new App password in the google account assigned for SMTP configuration, and put it in Backendless…Tested and that appears to have fixed it…
THANKS FOR ALL YOUR HELP!