[receiver/azuremonitorreceiver] Add support for authenticating using AD workload identity #24451
Assignees
Labels
Comments
cmergenthaler
added
enhancement
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Sep 3, 2023
This was referenced Sep 6, 2023
This was referenced Sep 12, 2023
codeboten
pushed a commit
that referenced
this issue
Sep 27, 2023
…24543) Enhances azuremonitor receiver authentication by using [azure workload identity](https://azure.github.io/azure-workload-identity/docs/). I have added a new config parameter `auth` to specify the used authentication method (default set to service-principal) in order to possibly add more methods in the future. Fixes #24451 **Testing:** Tested on my AKS
jmsnll
pushed a commit
to jmsnll/opentelemetry-collector-contrib
that referenced
this issue
Nov 12, 2023
…pen-telemetry#24543) Enhances azuremonitor receiver authentication by using [azure workload identity](https://azure.github.io/azure-workload-identity/docs/). I have added a new config parameter `auth` to specify the used authentication method (default set to service-principal) in order to possibly add more methods in the future. Fixes open-telemetry#24451 **Testing:** Tested on my AKS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/azuremonitor
Is your feature request related to a problem? Please describe.
Currently, the receiver can only authenticate using an azure service principal.
Describe the solution you'd like
Using managed identity and azure workload identity would be more secure
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: