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

401 Unauthorised but able to hit with curl+token #111

Open
mikeeaton83 opened this issue Jun 21, 2021 · 2 comments
Open

401 Unauthorised but able to hit with curl+token #111

mikeeaton83 opened this issue Jun 21, 2021 · 2 comments

Comments

@mikeeaton83
Copy link

Hi - I have the following issue:

When any of the checks run using token auth I get the following error:

Unable to authenticate the request due to an error: [invalid bearer token, square/go-jose: error in cryptographic primitive]\n

This is on a fresh kubernetes cluster - I've recreated the token / secret many times - I can use the token as a bearer with curl and this works absolutely fine. What can I do?

@mikeeaton83
Copy link
Author

So - although I've been completely ignored.. I've done some more testing after rebuilding my entire kubernetes cluster. If I use token substitution (labels) and pass in the bearer token and uri as labels I get an unauthorised error, if I pass in the actual token instead of using substitution it works fine.. can this please be looked at?

@sensu-discourse
Copy link

This issue has been mentioned on Sensu Community. There might be relevant details there:

https://discourse.sensu.io/t/kubernetes-plugin-unauthorised-when-using-labels-token-substitution-but-fine-when-not/2648/1

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

2 participants