You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have one pagerduty account configured through scoped oauth credentials and I am noticing that these credentials stop working after some time until I restart the backstage backend.
Initially, it can fetch services via the pagerduty.com/service-id annotation but after a day or two, when I visit the same component I get Missing or invalid PagerDuty Token and a 401 error with the following message:
{
"errors": [
"Failed to get service. Caller did not supply credentials or did not provide the correct credentials."
]
}
When I see this, if I just restart Backstage it starts working again with no issues.
The configuration I am using is:
pagerDuty:
oauth:
clientId: ${PD_CLIENT_ID}
clientSecret: ${PD_CLIENT_SECRET}
subDomain: ${PD_ACCOUNT_SUBDOMAIN} # just the subdomain part as stated in the docs
Expected behavior
The pagerduty integration works continuously without having to restart the backend.
Describe the bug
I have one pagerduty account configured through scoped oauth credentials and I am noticing that these credentials stop working after some time until I restart the backstage backend.
Initially, it can fetch services via the
pagerduty.com/service-id
annotation but after a day or two, when I visit the same component I getMissing or invalid PagerDuty Token
and a401
error with the following message:When I see this, if I just restart Backstage it starts working again with no issues.
The configuration I am using is:
Expected behavior
The pagerduty integration works continuously without having to restart the backend.
Screenshots
versions
Additional context
The text was updated successfully, but these errors were encountered: