Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
busunkim96 opened this issue Jun 24, 2021 · 4 comments · Fixed by #935
Closed

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

busunkim96 opened this issue Jun 24, 2021 · 4 comments · Fixed by #935
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@busunkim96
Copy link
Contributor

@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.

@busunkim96 busunkim96 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 24, 2021
@parthea parthea added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 25, 2021
@parthea
Copy link
Contributor

parthea commented Jun 25, 2021

Raising priority to P1 as we're blocking releases due to this bug.

@arithmetic1728
Copy link
Collaborator

working on it now

@parthea
Copy link
Contributor

parthea commented Jun 25, 2021

Thanks so much!

@arithmetic1728
Copy link
Collaborator

Created a PR to fix this: #935

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants