You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
:description: Implements both ``configauth.ServerAuthenticator`` and ``configauth.ClientAuthenticator``. It can be used in both http and gRPC exporters inside the ``auth`` settings to embed a static token for every RPC call made.
9
9
10
-
The Splunk Distribution of the OpenTelemetry Collector supports the Authenticator - Bearer extension. Documentation is planned for a future release.
10
+
The ``bearertokenauth`` extension implements both ``configauth.ServerAuthenticator`` and ``configauth.ClientAuthenticator``. It can be used in both http and gRPC exporters inside the ``auth`` settings to embed a static token for every RPC call made.
11
+
12
+
The following is required:
13
+
14
+
* You need to set the authenticator type to ``bearertokenauth``.
15
+
16
+
* You need to enable transport layer security on the exporter.
17
+
18
+
Get started
19
+
======================
20
+
21
+
Follow these steps to configure and activate the component:
22
+
23
+
1. Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
24
+
25
+
- :ref:`otel-install-linux`
26
+
- :ref:`otel-install-windows`
27
+
- :ref:`otel-install-k8s`
28
+
29
+
2. Configure the ``bearertokenauth`` extension as described in the next section.
30
+
3. Restart the Collector.
31
+
32
+
Configuration options
33
+
--------------------------------------------
34
+
35
+
The following configuration options are available:
36
+
37
+
* ``filename``. Name of file that contains the authorization token sent in every client call.
38
+
39
+
* ``token``. Static authorization token sent on every gRPC client call as metadata. The value of the token is prepended by ``${scheme}`` before being sent as a value of the authorization key in the request header (for HTTP) and metadata (for gRPC).
40
+
41
+
.. note:: Either ``filename`` or ``token`` are required. If both are specified, then the ``token`` field value is ignored.
42
+
43
+
Optionally, you can also configure:
44
+
45
+
* ``scheme``. ``Bearer`` by default. Specifies the auth scheme name.
46
+
47
+
Sample configuration
48
+
--------------------------------------------
49
+
50
+
To activate the component add ``bearertokenauth`` to the ``extensions`` section of your configuration file and include the extension in any pipeline of the ``service`` section. For example:
To find information about this component in the meantime, see :new-page:`Authenticator Bearer extension <https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/bearertokenauthextension>` on GitHub.
0 commit comments