-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logInWith() google oauth gives error 252 this authentication method is unsupported #1961
Comments
I too am receiving this error when trying to implement Google Oauth. I have the token from Google, but I get the exact same thing. |
You have to pass in the |
I'm already passing the
|
can you try with |
No news in 20 days, closing. |
@flovilmart i am trying to use google oath for login/signup and getting the following error. this is also added in configuration. 2016-11-08T14:34:28.586045+00:00 heroku[router]: at=info method=POST path="/server/users" host=espressoft-parse-server.herokuapp.com request_id=c398099d-5188-435f-8b82-0f89c8b1301b fwd="49.248.139.244" dyno=web.1 connect=0ms service=58ms status=404 bytes=549 Do you have any suggestions on this? |
@Jhonemarkus What solution you found for "This authentication method is unsupported."? |
Was anyone able to resolve this issue? |
Try using id_token instead of access token in your login payload. |
I tried the following but still getting the issue and on the server side I am seeing: |
@dondragon2 This is what worked for me... |
@junal I am trying to do a google login. the facebook login works fine |
did the google interface ( what API for "authData" when vendor is 'google' ) ever get resolved? I tried a bunch of permutaions for authData obj content and they all fail on a variety of errors ( stdout belo )
|
@rowntreerob the authData you're sending from the client is invalid. As you can see here:
Should be
|
fixed the fields (authData) and tried again using curl for the post , it is still failing - IMO - as the parse user does not yet exist, this POST should create a new row in _User where "userName" = {{ google.id }} and where authData field below gets copied into parseUser column "authData" .. but it errors out instead.
|
As mentioned above, accessToken should be in snake_case |
using "id" , "access_token" in the interface does not change the response to the post to "parse/users"...
|
Try using the idToken and send it to parse-server as id_token |
no change on using id_token in interface with the corresponding value supplied by firebaseUI... on each attempt i make 2 tries using both "uid" and "provider[0].uid" as the "id" value in the parse/user call. I suspect/guess that google wants me to be using "provider[0].uid" see first of the 2 images above for the JSON details coming from firebaseUI call...
|
I’m not sure this is an issue with parse server, as we’re using the google login in a production app and it’s working as expected. Open a question on stackoverflow as it may be more fitting than here. Thanks. Note that the google login is expected to work with the google auth SDK’s and android, not fire base. |
OK.. firebaseUI not compatible/interoperable with parse-server... I get it now. thanks |
You can always provide you own custom authAdapter on parse-server to support it Have a look into the auth adapters folder, and there’s only one method to implement to support your fire base UI credentials. It’s not because out of the box those credentials aren’t supported that you’re completely locked out. The best part, you can bring your own auth adapter without changing any internal code. |
will give that a try ... thank you |
Did not need a new adapter for firebaseUI - just more accurate mapping. It finally worked ( i think it was a combined mapping issue firebaseUI.CB vs authData values && provider scopes issue ) stdout below shows mapping of authData field values ( id, access-token):
|
Glad to hear it worked. |
I'm trying to login with Google oauth. The Google login goes OK but when I try to login to Parse it gives me the error.
My Parse-server init:
And on the client app (JS):
Logs/Trace
The server log:
The text was updated successfully, but these errors were encountered: