Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Low expires for JWT token. Why? Configurable? #5072

Open
WilliamDEdwards opened this issue Dec 2, 2024 · 0 comments
Open

Low expires for JWT token. Why? Configurable? #5072

WilliamDEdwards opened this issue Dec 2, 2024 · 0 comments

Comments

@WilliamDEdwards
Copy link

WilliamDEdwards commented Dec 2, 2024

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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant