InfluxDB behind authenticating reverse proxy

I am trying too setup up influx persistence on Openhab2.

I have had a influxdb running on a cloud server for a long time, and I would like to use it for persistence in OpenHAB2.
It’s configured to run behind apache configured as a reverse proxy server, doing both the SSL/TLS offloading (decrypt) and authentication using basic auth.

It looks like OpenHAB’s influxdb service is trying to authenticate using query parameters as seen in the apache log here: - - [12/Nov/2018:14:00:00 +0100] “POST /write?u=roth&p=<MyPa$$word>&db=openhab&rp=autogen&precision=n&consistency=one HTTP/1.1” 401 793 “-” “okhttp/2.4.0” - roth [12/Nov/2018:14:00:03 +0100] "POST /write?db=roth HTTP/1.1" 204 4176 "-" "curl/7.40.0" - fjernv [12/Nov/2018:14:00:04 +0100] "POST /write?db=roth HTTP/1.1" 204 4176 "-" "curl/7.40.0"

(First line is OpenHAB, second and third is my own script for other use).

Is there any way to make the influx persistence service use basic authentication as recommended by influx:
"Authenticate with Basic Authentication as described in RFC 2617, Section 2

This is the preferred method for providing user credentials."

Switching to basic authentication both has the benefit of making OpenHAB influx service, working with InfluxDB’s running behind authenticating reverse proxy’s and also avoid logging the password in CLEAR TEXT in the proxy logs (as seen in the log excerpt above).

Okay quick update. I made a workaround.

Since OpenHAB is always using the same username and password, I simply made a apache regex that match that.
Simple vhost:

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
     <Location /ping>
    Order deny,allow
    Allow from all
    Satisfy any
     <Location />
    <If "%{QUERY_STRING} !~ /u=openhab&p=MyPa$$word&db=openhab/">
    AuthType Basic
    AuthName "Restricted Content"
    AuthUserFile /etc/apache2/.htpasswd
    Require valid-user
    ProxyPass / http://localhost:8086/

The /ping Location is because the initial ping request does not use passwords.
This does only work on apache 2.4+ since the “If” function is not pressent in apache 2.2.

Hope it can be of use for some.