forked from open-telemetry/opentelemetry-collector
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes open-telemetry#2101 Signed-off-by: Juraci Paixão Kröhling <[email protected]>
- Loading branch information
1 parent
396948f
commit 5e4ddd4
Showing
32 changed files
with
771 additions
and
441 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,36 @@ | ||
# Authentication configuration for receivers | ||
|
||
This module allows server types, such as gRPC and HTTP, to be configured to perform authentication for requests and/or RPCs. Each server type is responsible for getting the request/RPC metadata and passing down to the authenticator. Currently, only bearer token authentication is supported, although the module is ready to accept new authenticators. | ||
This module allows server types, such as gRPC and HTTP, to be configured to perform authentication for requests and/or RPCs. Each server type is responsible for getting the request/RPC metadata and passing down to the authenticator. | ||
|
||
The currently known authenticators: | ||
|
||
- [oidc](../../extension/authoidcextension) | ||
|
||
Examples: | ||
```yaml | ||
extensions: | ||
oidc: | ||
# see the blog post on securing the otelcol for information | ||
# on how to setup an OIDC server and how to generate the TLS certs | ||
# required for this example | ||
# https://medium.com/opentelemetry/securing-your-opentelemetry-collector-1a4f9fa5bd6f | ||
issuer_url: http://localhost:8080/auth/realms/opentelemetry | ||
audience: account | ||
|
||
receivers: | ||
somereceiver: | ||
grpc: | ||
authentication: | ||
attribute: authorization | ||
oidc: | ||
issuer_url: https://auth.example.com/ | ||
issuer_ca_path: /etc/pki/tls/cert.pem | ||
client_id: my-oidc-client | ||
username_claim: email | ||
otlp/with_auth: | ||
protocols: | ||
grpc: | ||
endpoint: localhost:4318 | ||
tls_settings: | ||
cert_file: /tmp/certs/cert.pem | ||
key_file: /tmp/certs/cert-key.pem | ||
auth: | ||
authenticator: oidc | ||
``` | ||
## Creating an authenticator | ||
New authenticators can be added by creating a new extension that also implements the `configauth.Authenticator` extension. Generic authenticators that may be used by a good number of users might be accepted as part of the core distribution, or as part of the contrib distribution. If you have interest in contributing one authenticator, open an issue with your proposal. | ||
|
||
For other cases, you'll need to include your custom authenticator as part of your custom OpenTelemetry Collector, perhaps being built using the [OpenTelemetry Collector Builder](https://github.com/open-telemetry/opentelemetry-collector-builder). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.