Registering a PagerDuty app with Scoped OAuth
Register an app on your PagerDuty account and give it Scoped OAuth functionality to obtain the Client ID and Client Secret.
Create the app
Name the app and turn on OAuth 2.0
The Add New App form opens on Info & Functionality.
- Name:
StackOne Integration - Description:
Integration with StackOne - Under Functionality, select OAuth 2.0.
- Click Next.

Choose Scoped OAuth
On Configure OAuth 2.0, pick the OAuth type under Authorization.
- Select Scoped OAuth. It grants access per resource type, rather than everything the authorizing user can reach.
- Leave Confidential client selected. StackOne keeps the Client Secret on its own servers and sends it on the token request.

Set the redirect URL
Under Redirect URL, click + Add Redirect URL.
- Redirect URL: the Callback URL from your Connector Profile
- PagerDuty compares the redirect URL with its saved value exactly, so copy it without changes.

Add the permission scopes
Under Permission Scope, find each resource in the table and select its Read Access or Write Access checkbox. Search Resource filters the table, and Total Resources Used counts the resources selected so far.
- Select every scope the connector requests. When an app requests a scope it does not hold, PagerDuty issues a token carrying only the
openidscope, and every API call then fails.

Copy the credentials
Click Register App. The OAuth 2.0 Client Information dialog opens with the credentials.
- Copy the Client ID into your Connector Profile.
- Copy the Client Secret into your Connector Profile.
- This is the only time the client information can be viewed or downloaded. The Client Secret cannot be retrieved later, so store it securely before closing the dialog.
- Click Continue.

Create the StackOne Connector Profile
Create a Connector Profile
Link an Account
