Skip to content

403 permission denied errors in some libraries with always_use_jwt_access = True #929

@busunkim96

Description

@busunkim96

@parthea noticed some library system and sample tests failing in PRs adding always_use_jwt_access (see #920)

There are three slightly different error messages:


  1. google.api_core.exceptions.PermissionDenied: 403 Provided scope(s) are not authorized


  1. google.api_core.exceptions.PermissionDenied: 403 The caller does not have permission


  1. google.api_core.exceptions.PermissionDenied: 403 User does not have sufficient permissions for this property. To learn more about Property ID, see https://developers.google.com/analytics/devguides/reporting/data/v1/property-id.

Sample tests in many other repositories did pass, and I do not see an obvious difference between these APIs and the ones above.

Metadata

Metadata

Labels

priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions