Bearertokenauth Extension
contrib, k8s
Maintainers: @frzifus
Source: opentelemetry-collector-contrib
Overview
This extension implements bothconfigauth.ServerAuthenticator and configauth.ClientAuthenticator. It can be used in both http and gRPC exporters inside the auth settings, as a means to embed a static token for every RPC call that will be made.
The authenticator type has to be set to bearertokenauth.
Configuration
-
header: Specifies the auth header name. Defaults to “Authorization”. Optional. -
scheme: Specifies the auth scheme name. Defaults to “Bearer”. Optional. -
token: Static authorization token that needs to be sent on every gRPC client call as metadata. -
tokens: A list of static authorization tokens, one of which needs to be sent on every gRPC client call as metadata. -
filename: Name of file that contains authorization tokens. The file is parsed line by line. On each line, the first whitespace-delimited string is treated as the token. Any text following the first whitespace is ignored and can be used for comments (e.g.,my-token # commentormy-token // comment). -
retry_on_failure: Optional. Controls retry behaviour during startup when the file referenced byfilenameis not yet available (e.g., the secret is mounted shortly after the collector starts).enabled: When true, startup waits for the file to appear instead of failing immediately. Defaults tofalse.max_retries: Maximum number of retry attempts before giving up. Set to0to retry indefinitely until the file appears. Defaults to0.interval: Interval between retry attempts (e.g.,1s,500ms). Defaults to0seconds.
-
wait_for_token_file: (Optional) When true, startup blocks until the token file is read successfully (respectingretry_on_failure) instead of retrying in the background. If the file cannot be read within the retry budget, the collector fails to start. Requiresretry_on_failure.enabledandfilenameto be set. Defaults tofalse.
token or filename field is required. If both are specified, then the token field value is ignored. In any case, the value of the token will be prepended by ${scheme} before being sent as a value of “authorization” key in the request header in case of HTTP and metadata in case of gRPC.
Note: bearertokenauth requires transport layer security enabled on the exporter.
Configuration
Example Configuration
Last generated: 2026-09-07