@@ -29,21 +29,15 @@ room at the [CNCF Slack workspace](https://slack.cncf.io).
29
29
30
30
## Architecture
31
31
32
- Authenticators are regular extensions that also satisfy one or more interfaces
33
- related to the authentication mechanism:
34
-
35
- - [ go.opentelemetry.io/collector/config/configauth/ServerAuthenticator] ( https://pkg.go.dev/go.opentelemetry.io/collector/config/configauth#ServerAuthenticator )
36
- - [ go.opentelemetry.io/collector/config/configauth/GRPCClientAuthenticator] ( https://pkg.go.dev/go.opentelemetry.io/collector/config/configauth#GRPCClientAuthenticator )
37
- - [ go.opentelemetry.io/collector/config/configauth/HTTPClientAuthenticator] ( https://pkg.go.dev/go.opentelemetry.io/collector/config/configauth#HTTPClientAuthenticator )
38
-
39
- Server authenticators are used with receivers, and are able to intercept HTTP
40
- and gRPC requests, while client authenticators are used with exporters, able to
41
- add authentication data to HTTP and gRPC requests. It is possible for
42
- authenticators to implement both interfaces at the same time, allowing a single
43
- instance of the extension to be used both for the incoming and outgoing
44
- requests. Note that users might still want to have different authenticators for
45
- the incoming and outgoing requests, so, don't make your authenticator required
46
- to be used at both ends.
32
+ [ Authenticators] are regular extensions that also satisfy one or more interfaces
33
+ related to the authentication mechanism. Server authenticators are used with
34
+ receivers, and are able to intercept HTTP and gRPC requests, while client
35
+ authenticators are used with exporters, able to add authentication data to HTTP
36
+ and gRPC requests. It is possible for authenticators to implement both
37
+ interfaces at the same time, allowing a single instance of the extension to be
38
+ used both for the incoming and outgoing requests. Note that users might still
39
+ want to have different authenticators for the incoming and outgoing requests,
40
+ so, don't make your authenticator required to be used at both ends.
47
41
48
42
Once an authenticator extension is available in the collector distribution, it
49
43
can be referenced in the configuration file as a regular extension:
@@ -170,3 +164,6 @@ as part of their own distributions. Fortunately, building a custom distribution
170
164
can be done using the
171
165
[OpenTelemetry Collector Builder](https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder)
172
166
utility.
167
+
168
+ [Authenticators] :
169
+ https://pkg.go.dev/go.opentelemetry.io/collector/config/configauth
0 commit comments