Google drive authentication required client id and client secret and then sign in (however i was stuck at that option after entering)
I actually came across with two different scenarios, one when i was connecting one of my google sheet with n8n node, it requires sign in which worked.
but second scenario required access google drive to store the element in the root. for that it asked for client id and client secret which needs to be created from google console.
Hey @enpipi_nah! Hope you are doing great!
Could you please confirm if your OAuth Redirect URL is already added to you Authorized redirect URI's in your Google Console? If don’t, you should see the OAuth 2.0 Client IDs at https://console.cloud.google.com/auth/clients and after click on the right one, add your OAuth Redirect URL under Authorized redirect URI’s:
That’s precisely my point. It’s confusing that Google Drive, Docs, and Spreadsheets—all Google services—use different authentication methods, and the inconsistency with Docs is a real problem.
Thank you. I know how to authenticate with GCP. However, when having my team members use it, I think “Sign in with Google” is preferable because it allows even less tech-literate members to use it easily.
I’m agree with you, documentation it’s a bit confusing in some cases and difficult to handle those configurations within the team members! Regarding to “ …it says that ‘Sign With Google’ can be used for Google Drive authentication, but it doesn’t appear Is the document old?“ It should be appear once you provide your client id and client secret!
