scoped oauth issues whilst testing locally

[BenjoGreeno]

Hello!

I already raised this in the community portal here, however I'm not sure whether that was the right place - apologies for spamming.

I'm testing this out via a local build and facing issues that look similar to issue #104. Here is the error output, followed by the set up details

[1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty accounts configuration found in config file. Reverting to legacy configuration. 
[1] 2024-09-12T13:08:40.054Z pagerduty warn No PagerDuty API token found in config file. Trying OAuth token instead... 
....
[1] 2024-09-12T13:08:40.356Z pagerduty error Unable to retrieve valid PagerDuty AUTH configuration from config file: Error: Failed to retrieve valid token. Bad Request - Invalid arguments provided. 

Some details

• There's a scoped oauth app set up on our PagerDuty account
• I've added environment variables for all the necessary bits and added the block to both the appconfig and appconfig-local yamls (including the our account subdomain)
• I've installed the frontend and backend plugins, plus added all the additional blocks as per the config (although the last bit probably doesn't matter so much as it's not getting passed authentication)

pagerDuty:
  oauth:
    clientId: ${PD_CLIENT_ID}
    clientSecret: ${PD_CLIENT_SECRET}
    subDomain: ${PD_ACCOUNT_SUBDOMAIN} 
    region: ${PD_ACCOUNT_REGION}

I was wondering whether I'm missing any additional config, does the above seem ok? Or whether I'm missing something obvious

Thanks in advance