-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[extension/bearertokenauth] Bearer token auth extension does not pick up the updated token from file #17031
Comments
/label extension/bearertokenauth |
Good catch. I see why: opentelemetry-collector-contrib/extension/bearertokenauthextension/bearertokenauth.go Lines 178 to 199 in 669a5b7
We should instead be calling |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm working on this. |
This is fixed in #17052. Closing this issue. |
Component(s)
extension/bearertokenauth
What happened?
Description
Bearer token auth extension is not picking up the updated token and instead it fetches the token once and that's re-used forever.
The issue is related to using bearer token auth for http clients and works fine for gRPC.
Steps to Reproduce
Expected Result
Request from the bearer token auth should have the updated bearer token.
Actual Result
Request from the bearer token auth has the old token.
When I used a valid token and tried to send data to a prometheus remote write EP, it failed with the following error:
Collector version
0.66.0
Environment information
Environment
OS: macOS Monterey
OpenTelemetry Collector configuration
Log output
Additional context
N/A
The text was updated successfully, but these errors were encountered: