influxdata / influxdata/kapacitor
[feature request] Be able to specify HTTP auth parameters when creating subscriptions
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Currently there is no way to have open-source Kapacitor embed HTTP auth credentials in a subscription. This can be useful for users who are routing subscriptions through a proxy, and enforcing authentication at the proxy layer (transparent to Kapacitor). Similar to the `kapacitor-hostname` and `kapacitor-port` configuration options available to `influxdb` blocks, a `http-auth-username` / `http-auth-password` option would be needed to inject user credentials when creating subscriptions.
For example, the configuration:
```
[[influxdb]]
http-auth-username = "myuser"
http-auth-password = "mypassword"
```
Would generate subscriptions with a target similar to:
```
http://myuser:mypassword@myhost.example.com:9092
```
Contributor guide
Research direction
Trace how influxdb block configuration is parsed and how subscriptions are created, starting with the existing kapacitor-hostname and kapacitor-port options. Check the subscription target construction and related tests, then verify that configured HTTP credentials produce the requested authenticated target without affecting configurations that omit them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100