Skip to content

Lack of required scopes might prevent that PagerDutyCard loads properly #134

Open
@t1agob

Description

@t1agob

Describe the bug
The PagerDuty plugin for Backstage, when configured with OAuth, requires the following scopes to work:

    abilities.read // used in scaffolder only
    analytics.read
    escalation_policies.read
    incidents.read
    oncalls.read
    schedules.read
    services.read
    services.write // used in scaffolder only
    standards.read
    teams.read
    users.read
    vendors.read // used in scaffolder only

If some of these scopes are missing (e.g. standards.read) the PagerDutyCard fails to load and causes to app to crash. This doesn't happen for all scopes as some will fail more gracefully.

To Reproduce
Steps to reproduce the behavior:

  1. Register an Application in PagerDuty
  2. When setting the Application Scopes select all of the ones above, except for standards.read.
  3. Run your Backstage application
  4. Open a Backstage entity that contains the PagerDutyCard

Expected behavior
When a required scope is missing I would expect the PagerDutyCard to fail gracefully and present a message saying which scopes are missing in the Application Registration so it can be fixed.

Screenshots
This is how we found out the problem was related to a missing scope 👇
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions