Here is the current flow I want to achieve:
-Click on the “Sign in” Google Button.
-Grant consent to the app for specific scopes (Gmail + GCalendar)
-Get redirected to the index page.
Here is the struggle:
I can successfully login with the Google plugin, but I cannot ask for specific scopes and store the (access + refresh) tokens.
Currently, I’m doing one after the other to have both the user logged in and its tokens stored, but in terms of UX, I have two consent screens. This is not natural at all.
Hi - That’s because in the video @wisebubbler is using ‘Oauth2 User-Agent Flow’ as the Authentication method, so Bubble ‘automagically’ handles the refresh token/new key part for you.
Whereas in the first set of instructions you followed Google Calendar API use case - #7 by mebeingken @mebeingken is using ‘Non or Self-handled’ so he had to build a workflow (which is detailed in that post) to handle the refresh token part.
I want the idtoken from google to perform next authentication with our login API.
Can we get accesstoken, idtoken in response from google?
when i run the just googleoauth in app it works properly. but i need the idtoken.
Do i need that extra APIenpoint call to get the token?
Thank you in advance…