-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
alerts:read Not a Valid Scope #82862
Labels
Comments
Assigning to @getsentry/support for routing ⏲️ |
Kobby-Bawuah
added
Sync: Jira
Apply to auto-create a Jira shadow ticket
Product Area: Alerts
labels
Jan 3, 2025
Routing to @getsentry/product-owners-alerts for triage ⏲️ |
getsantry
bot
moved this from Waiting for: Support
to Waiting for: Product Owner
in GitHub Issues with 👀 3
Jan 3, 2025
Thanks for bringing this to our attention. We're working on a fix. |
The fix has been implemented. Let me know if the issue still persists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I have had at least two user reach out about a 400 error when attempting to set permissions for the Alerts field in a custom integration. The error response was:
The error reponse is "{"scopes":["alerts:read not a valid scope"]}"
Sample user case: https://sentry.zendesk.com/agent/tickets/141044
Steps to Reproduce:
Expected Result
The Alerts field should allow permissions such as Read or Read & Write without resulting in a 400 error.
Actual Result
Attempting to set permissions for the Alerts field results in the alerts: read not a valid scope error.
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: