Reference
PagerDuty
Set up PagerDuty OAuth for incident management and on-call scheduling
Overview
Section titled “Overview”Connect your users to PagerDuty for incident management, on-call scheduling, alert routing, and service health monitoring.
| Property | Value |
|---|---|
| Provider ID | pagerduty |
| Category | Developer Tools |
| PKCE | Supported |
| Token refresh | Automatic |
| Redirect URI | Shown in Developer Portal |
Step 1: Create a PagerDuty OAuth App
Section titled “Step 1: Create a PagerDuty OAuth App”Go to the PagerDuty Developer Portal
Sign in to PagerDuty App Registration. The PagerDuty OAuth2 documentation describes the setup fields.
Register the application
Go to Integrations > App Registration and register a new app. Select OAuth 2.0 as the authorization type.
Configure the redirect URI
Add the Alter callback URL from the Developer Portal to the Redirect URLs field.
Get credentials
Copy the Client ID and Client Secret.
Step 2: Add to Alter Vault
Section titled “Step 2: Add to Alter Vault”Open the Developer Portal
Go to portal.alterauth.com and navigate to the application.
Add PagerDuty provider
Go to OAuth Providers > Add Provider > PagerDuty.
Enter credentials
- Client ID: Paste your PagerDuty Client ID
- Client Secret: Paste your PagerDuty Client Secret
Select scopes
Choose the scopes the application needs.
Save
Click Save. The provider is now active.
Available Scopes
Section titled “Available Scopes”| Scope | Description |
|---|---|
openid | Access to user identity information |
read | Read access to PagerDuty resources |
write | Write access to PagerDuty resources |
- See the PagerDuty OAuth2 documentation for more details.
Policy-cataloged operations
Section titled “Policy-cataloged operations”Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.
| Operation ID | Families | Method | Provider path |
|---|---|---|---|
listIncidents | read | GET | /incidents |
getIncident | read | GET | /incidents/{id} |
createIncident | send, write | POST | /incidents |
updateIncident | write | PUT | /incidents/{id} |
updateIncidents | write | PUT | /incidents |
mergeIncidents | write | PUT | /incidents/{id}/merge |
createIncidentNote | write | POST | /incidents/{id}/notes |
listIncidentNotes | read | GET | /incidents/{id}/notes |
createIncidentStatusUpdate | send | POST | /incidents/{id}/status_updates |
createIncidentNotificationSubscribers | write | POST | /incidents/{id}/status_updates/subscribers |
listServices | read | GET | /services |
createService | write | POST | /services |
updateService | write | PUT | /services/{id} |
deleteService | delete | DELETE | /services/{id} |
listUsers | read | GET | /users |
getUser | read | GET | /users/{id} |
createUser | admin | POST | /users |
deleteUser | admin, delete | DELETE | /users/{id} |
listSchedules | read | GET | /schedules |
getSchedule | read | GET | /schedules/{id} |
listOnCalls | read | GET | /oncalls |
listEscalationPolicies | read | GET | /escalation_policies |