Hmmh, that would require just a tad of refactoring. Plugin version 3.0 changed credentials management to use the credentials-plugin and the InfluxDBClientOptions are created (username and password parsed, organization and bucket assigned) before creating the InfluxDB connection. My near future is a bit busy, so this will probably hang until the end of summer.

I would be great if you could do that, for me it would mean that I can use it in my current project

I'm also hitting this issue with InfluxDB OSS 2.0 so it doesn't only affect cloud. I'm unable to get basic auth working for my instance, not sure if I need to configure something on my installation to enable it. I was able to get basic auth working, but I'd rather use tokens which have better access control.

Helow cengler! Could share what you have done to connect with InfluxDB 2.0? Thanks!

I created a "Username and password" credential that can be used to login to my InfluxDB instance and used that in the credential setting of the plugin.

Than you!! 

cengler how did you get it working?  For me I cannot get user/pass auth to work with the latest plugin.  I have replciated in the influxdb-client-java version used by the plugin.  It's quite an old one 1.15.0

Pull Request 126 created to add support for authentication token authorization. Waiting for Jenkins checks to pass before merging.

PR merged. Feature will be available in next release.

InfluxDB plugin 3.1 adds support for token based authentication.