Oauth2 Scoped Token isn't working due to invalid scope

[nakulrao]

Hi there,

I'm having some issues with the Oauth 2.0 Scoped Token authentication. It's complaining that there are invalid scopes however the provider has no parameters to accept scopes as part of the configuration.

Terraform Version

Terraform v1.9.7
on darwin_arm64

Affected Resource(s)

• use_app_oauth_scoped_token

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

provider "pagerduty" {
  use_app_oauth_scoped_token {
    pd_client_id     = var.pd_client_id
    pd_client_secret = var.pd_client_secret
    pd_subdomain     = var.pd_subdomain
  }
}

Debug Output

https://gist.github.com/nakulrao/0fd63a71714e1d8c704374a306ed673b

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

What should have happened?

It should authenticate given that the Scoped OAuth client_id and client_secret are correct. I've tested using the API and am able to authenticate and return an access_token.

Actual Behavior

What actually happened?

failed to prep request: oauth2: "invalid_request" "Invalid scope"

I believe this is because we're not passing in a scope as part of the Authentication flow to PagerDuty

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform plan

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• PagerDuty API requires scopes to be requested when Authenticating using Scoped OAuth: https://developer.pagerduty.com/docs/e518101fde5f3-obtaining-an-app-o-auth-token

[nakulrao]

Turns out it was due to incorrect subdomain