Hello there!
The solution for me was to create a fixed redirect page in between my app and google o auth.
in this way, the flow is as follows:
my login page sends the request to my fixed redirect page with the callback url as a parameter;
My fixed redirect page (inserted and authorized in Google as http://myapp.bubble.io/loginredirectpage) speaks with google, authenticate the user and get it back to bubble
I am currently facing this issue as well. Do you mind sharing a little more about this?
From my understanding, you redirect the page to your static redirect page (that are registered in Google console) when you click on the login workflow right? But how did you include the parameter in the URL when this parameter itself is dynamic and you can’t explicitly register this URL with the parameter in Google Console? Thanks.
hey @jeff.chia1995 can you be more specific with your use case ? What do you want to do ? redirect the user to a page where he was when he was trying to loggued in with Google?
If so, you can have a temp field on the user datatype to store a chunck of url (like url parameters) to get it him back to where he was.*
But before even getting to that, I am not able to log the user in from any pages.
From my understanding from here ([New Feature] Using a generic redirect URL for OAuth providers - #12 by d.norkus) , as soon as you tick the box and put that URI into the google console, user should be able to sign in from any pages in the site, am I understanding this correctly?
I had put in all different combinations of the URI but I’m still getting error when signing user in. And in my workflow, this is all I do.