-
Notifications
You must be signed in to change notification settings - Fork 673
Open
Description
Description
When running gws auth login -s people (or including people in the services list), the resulting OAuth token does not include the https://www.googleapis.com/auth/contacts scope. This means all People API calls that require the contacts scope fail with a 403 "insufficient authentication scopes" error.
Steps to Reproduce
gws auth login -s gmail,calendar,drive,docs,sheets,tasks,people- Approve all scopes in the consent screen
gws auth status— no contacts scope in the tokengws people people connections list --params '{"resourceName": "people/me", "personFields": "names"}'— returns 403
Expected Behavior
The people service should map to https://www.googleapis.com/auth/contacts (or contacts.readonly) during auth, so that People API calls work after authentication.
Environment
- gws version: 0.8.0
- Account type: personal @gmail.com
- OAuth app: unverified (testing mode), People API enabled in Cloud Console, contacts scope added to consent screen
Workaround Attempted
- Adding the contacts scope to the OAuth consent screen in Google Cloud Console — does not help because
gwsdoes not include it in the OAuth authorization URL - Passing the raw scope URL (
https://www.googleapis.com/auth/contacts) to-s—gwsignores it
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels