[
https://issues.apache.org/jira/browse/BAHIR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567660#comment-17567660
]
ASF subversion and git services commented on BAHIR-284:
-------------------------------------------------------
Commit d7d3e5d663299521276beead871d90730cb08270 in bahir-flink's branch
refs/heads/master from dave
[ https://gitbox.apache.org/repos/asf?p=bahir-flink.git;h=d7d3e5d ]
[BAHIR-284] Add option to use token authentication for influxdb2
> Support Token Authentication for InfluxDB2 connector
> ----------------------------------------------------
>
> Key: BAHIR-284
> URL: https://issues.apache.org/jira/browse/BAHIR-284
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Affects Versions: Flink-1.0
> Reporter: David Quigley
> Priority: Major
> Fix For: Flink-Next
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The org.apache.flink.streaming.connectors.influxdb.sink.InfluxDBSinkOptions
> class only supports username and password for authentication. This results in
> basic authentication being used by the underlying
> com.influxdb.client.InfluxDBClient instance. If the influxdb instance
> restarts, the session token retrieved from the basic authentication flow
> expires, resulting in all subsequent writes failing.
> The access token is a more durable authentication method. A token option
> should be added to the
> org.apache.flink.streaming.connectors.influxdb.sink.InfluxDBSinkOptions class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
