-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for OAuth for Elastic Search exporter #29329
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Good idea. There's an existing oauth extension that could be used for this, but it requires exporters to use the standard HTTP exporter configuration module. The elastic search exporter currently defines all of its own configuration options, rather than relying on the standard package. The code owners would have to look into the effort required here to move to use the standard library, and this would probably be a breaking change, but I think this is a valid request. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/elasticsearch
Is your feature request related to a problem? Please describe.
Yes due to firm wide security policy our requirements firm cannot use basic Auth or apk-key option for authentication.
Describe the solution you'd like
Allow mechanism for this component to use OAuth as an authentication method.
Describe alternatives you've considered
Basic Auth and api-kay
Additional context
No response
The text was updated successfully, but these errors were encountered: