integration_google icon indicating copy to clipboard operation
integration_google copied to clipboard

Credentials OAuth consent screen different to installation doc

Open ggrobi opened this issue 3 years ago • 5 comments

Tried following the installation documentation but the Google interface is completely different from documentation. Is there an updated version or am I in the completely wrong area? See screenshot image

ggrobi avatar Jan 23 '21 06:01 ggrobi

Hi, there is no need to configure an "OAuth consent screen". The procedure is up to date, I just checked in google console interface. You just need to go in "Credentials" (left sidebar) and follow the instructions in Nextcloud "connected accounts" admin settings section.

Any better?

julien-nc avatar Jan 23 '21 14:01 julien-nc

Same happens to me @ggrobi , no way to follow up the procedure. Can you Double check @eneiluj ? Thnks

crcerdas avatar Feb 07 '21 12:02 crcerdas

I tried to create a new google account and set it all up. For some reason, when visiting https://console.developers.google.com I'm redirected to https://console.cloud.google.com and the consent screen configuration becomes mandatory...

I've managed to configure everything and get this app work.

They make it awfully complicated... And there are a lot of restrictions. Make sure you read the explanations about "Publishing status" and "User type".

So you need to create an OAuth app. Set the "user type" to "external". You can leave the "App domain" section empty. If your Nextcloud domain is my.nextcloud.example.org, then set the "Authorized domains" field to example.org. (just the top domain and the first subdomain. Then, when asked for the scopes, enter this in the "Manually add scopes" field:

openid
profile
https://www.googleapis.com/auth/calendar.readonly
https://www.googleapis.com/auth/calendar.events.readonly
https://www.googleapis.com/auth/contacts.readonly
https://www.googleapis.com/auth/photoslibrary.readonly
https://www.googleapis.com/auth/drive.readonly

and press "Add to table". In "Test users" section, add yourself (your google account) as a test user.

Once that is done, you should be able to follow the procedure about the "Credentials" section. Don't forget to "enable" the APIs in the "Library" section. Good luck. Feel free to ask questions :grin:.

julien-nc avatar Feb 08 '21 17:02 julien-nc

This app is great! The setup was confusing and difficult though, because the documentation was outdated. I did it like this:

Google Cloud Platform

  • Create new Nextcloud project
    • Create new OAuth Consent Screen
      • Add gmail address of Nextcloud user to test users
    • Add APIs to Nextcloud project
      • People API
      • Google Drive API
      • Photos Library API
      • Google Calendar API

Nextcloud Instance

  • Settings > Connected Accounts > Google Integration
  • Settings > Data Migration > Google Login

Redsandro avatar May 04 '21 12:05 Redsandro

I'd like to add, that I also needed to activate the needed API's (People, Drive, Photos, Calendar) here: https://console.cloud.google.com/apis/library Simply adding the scopes was not enough.

netzwerch avatar Nov 12 '21 12:11 netzwerch

In "Test users" section, add yourself (your google account) as a test user.

But does that mean I have to add every user of my Nextcloud instance that might want to migrate their stuff as a test user?! I tried to get the app out of Testing status using using "Publich app" under the publishing status of the OAuth consent screen but that just requires to meet some outrageous demands.

paulvt avatar Feb 24 '23 14:02 paulvt

Hello :wave: This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment or remove the label to avoid it getting closed.

Cheers :blue_heart:

github-actions[bot] avatar Jun 03 '23 02:06 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar Jun 08 '23 02:06 github-actions[bot]