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
Since upgrading to Sensu 6.12, scripts running sensuctl are failing with:
Error: API error: failed to request new refresh token; client returned 'The server returned the error: 401 Request unauthorized'
Looking at .config/sensu/sensuctl/cluster (where sensuctl stores tokens), I discovered that expires_at is set 5 minutes.
First of all: was the validity period changed? I can't tell, as this version has no documentation nor release notes: sensu/sensu-docs#4215. We've not experienced any issues before Sensu 6.12, though.
Since upgrading to Sensu 6.12, scripts running
sensuctl
are failing with:Looking at
.config/sensu/sensuctl/cluster
(wheresensuctl
stores tokens), I discovered thatexpires_at
is set 5 minutes.First of all: was the validity period changed? I can't tell, as this version has no documentation nor release notes: sensu/sensu-docs#4215. We've not experienced any issues before Sensu 6.12, though.
Second of all: is the validity period changeable? It's overly short, and therefore impractical. We don't call
sensuctl
every 5 minutes, nor do we want to. https://docs.sensu.io/sensu-go/latest/observability-pipeline/observe-schedule/backend/#backend-configuration-options doesn't show a configuration option.The text was updated successfully, but these errors were encountered: