influxdata/telegraf

OAuth2 Authentication with http_response

Open

#16,644 建立於 2025年3月16日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Go (9,892 star) (4,161 fork)batch import
feature requesthelp wantedsize/s

描述

Use Case

I would like to use the http_response plugin with OAuth2 authentication

Expected behavior

Add OAuth2 authentication to http_response base on the existing code from the http plugin

OAuth2 Client Credentials. The options 'client_id', 'client_secret', and 'token_url' are required to use OAuth2. client_id = "clientid" client_secret = "secret" token_url = "https://indentityprovider/oauth2/v1/token" scopes = ["urn:opc:idm:myscopes"

Actual behavior

No OAuth2 authentication is directly available

Additional info

No response

貢獻者指南

技術棧
go
領域
authenticationbackendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programming basicsOAuth2 Client Credentials flowTelegraf plugin development
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
First, examine the existing OAuth2 authentication implementation in the http input plugin, located in plugins/inputs/http/ (likely in a file like oauth2.go or http.go). Understand how it configures client id, client secret, token url, and scopes. Then, look at the http response output plugin (plugins/outputs/http response/) to see its current structure. The goal is to replicate the OAuth2 configuration and token handling from the input plugin into the output plugin. Pay attention to the plugin registration, configuration parsing, and HTTP client creation. There is one comment on the issue that may contain additional guidance.