social login throwing 401 after changing google client ID and secret about spring-lemon HOT 8 CLOSED

Strange. Help wanted if anyone else can try and reproduce the issue...

from spring-lemon.

Can you also help me implement the same social login via mobile apps. As the auth token returned by them is different and throws 401 when passing to get Context

from spring-lemon.

I've no idea on mobile apps and how they would be different. Could you please explain what's the exact issue and how Spring Lemon could support this you think?

from spring-lemon.

Hi, thanks for the reply.
Let me explain in detail:
When we hit this api: /oauth2/authorization/google (For login using Google via web browser)
we are expecting code from google auth on this endpoint : /login/oauth2/code/google. Right?
Then an auth token is generated and user is redirected to this end point with access token (which can be exchanged with an Access token using getContext API) : /social-login-success?token

But, in mobile devices we use Google sdk for login which returns auth code to our app, and not on our server end point which is (/login/oauth2/code/google). How can I use this code to generate access token for that particular code.

Any help will be appreciated as I am stuck with this from past 3 days. BTW thanks for the amazing library. +1

from spring-lemon.

Not sure how to support it. But why do you use the Google SDK? Why not the server endpoint, just like a webapp? Hope your app is cookie enabled.

from spring-lemon.

from spring-lemon.

Ok, thanks for posting the solution -- it might help others. However, I still have a question: you'll then need to code the social login in Android/iOS -- separately for each Google, Feacbook, GitHub ...? What's the exact problem in using the server redirects instead, just like web applications?

from spring-lemon.

Mobile devices use sdks for these social logins. Hence no server redirects. Thanks for the help.

from spring-lemon.