Google SSO Issues

Ask us anything
, ,
1

I have been banging my hed against the wall for days now - I am trying to implement the Google SSO and running into strange issue

I am calling the /oauth/google/init and receiving the code back, once the code is received I am calling the /oauth/google/continue
through a Workflow that passes the CODE and the redirect URI (properly registered as Authorized redirect URIs) to the API

The debugger show the workflow being triggered BUT I do not see any equivalent call on the XANO side

Here is the squence of screens

screen1
screen1986×752 164 KB

screen2
screen21102×443 28 KB

screen3
screen31455×752 76.9 KB

screen4
screen41876×833 122 KB

If I run the worflow manually right after having recevied the call, then the API call hits XANO

screen5
screen51681×851 138 KB

Can anybody offer their two cents of why this is happening?

Thank you

Elena

2

Ok - out of desperation I added a DELAY prior calling the /oauth/google/continue and the call hits XANO NOW!!! And it works beautifully

I am wondering

screen6
screen61103×775 66 KB

screen7
screen71883×668 110 KB

if anybody has had this issue? Also this solution seems VERY precarious - @WeWeb - any thoughts??

Attached screens for proof

3

Interesting! Thanks for sharing the tip. I don’t see the delay you added in your second screenshot. Would you mind sharing where you added the delay? Is it after the “Setting value for code” action in the previous workflow?