You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal:
I'm seeing implementations where additional (basic) authentication proxies are being placed in front of InfluxDBs (mainly 1.8 versions where auth is disabled). This makes it difficult to use the compatibility API as basic auth headers cannot be added, only the Authorization: Token {user}:{pwd} would be added. As described here.
Would it be possible to also pass a Basic Auth header so that a auth proxy would be able to process the API requests in such cases?
Current behavior:
Writing to the compatibility API to a InfluxDb 1.8 which has auth disabled but uses a proxy with basic auth is not possible
Desired behavior:
It would be good to allow these special setups with authenticating proxies and influxdbs with not auth enabled
Alternatives considered:
Reverting to either not use the new influxdb-client or manual line protocol posting with basic auth (not very efficient)
Use case:
It would help in migrating solutions that need to write to both 1.8 (with special setups) and 2.0 influxDBs
The text was updated successfully, but these errors were encountered:
Proposal:
I'm seeing implementations where additional (basic) authentication proxies are being placed in front of InfluxDBs (mainly 1.8 versions where auth is disabled). This makes it difficult to use the compatibility API as basic auth headers cannot be added, only the
Authorization: Token {user}:{pwd}
would be added. As described here.Would it be possible to also pass a Basic Auth header so that a auth proxy would be able to process the API requests in such cases?
Current behavior:
Writing to the compatibility API to a InfluxDb 1.8 which has auth disabled but uses a proxy with basic auth is not possible
Desired behavior:
It would be good to allow these special setups with authenticating proxies and influxdbs with not auth enabled
Alternatives considered:
Reverting to either not use the new influxdb-client or manual line protocol posting with basic auth (not very efficient)
Use case:
It would help in migrating solutions that need to write to both 1.8 (with special setups) and 2.0 influxDBs
The text was updated successfully, but these errors were encountered: