-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
OAuth2 Secret store does not work #15530
Comments
Hi, Can you try the artifacts in #15531 in 20-30mins? There will be a comment added by the Tiger bot with some artifacts you can download and let us know if it resolves the issue? I was able to reproduce locally with your config (thank you) and once I made this change was able to start up successfully. |
wow, you are blazing fast :-) absolutely. i can check it. is there a macos version i can download? |
Yep! Assuming you are on an Apple Silicon mac: Here is the tiger bot comment with a full array of other downloads. |
nice. the error is gone!! :-) unfortunately it still does not work, but i assume thats a configuration mistake (i guess the bearer token authentication with base64(id + secret) is the problem). i will check it out. thanks for your support! |
okay, the problem is, that the oauth-endpoint expects a Bearer-Authentication-Token that consists of id:secret (base64). obviously telegraf does not provide this auth-header. any idea how to solve that issue? |
@srebhan - can you comment on this tomorrow, thanks |
@mimez could you please open a feature request to add bearer-token auth?! |
Relevant telegraf.conf
Logs from Telegraf
System info
telegraf 1.31.0 on macos
Docker
No response
Steps to reproduce
Expected behavior
either it should report an readable error or it should work
Actual behavior
a stack trace appears
Additional info
No response
The text was updated successfully, but these errors were encountered: