Use basic auth

[robertlabrie]

Because reasons, we have to access InfluxDB through nginx as a rev proxy with basic auth and not at the root, so this introduces two big changes:

1. A thing called baseUrl which if specified is used in place of the connection options: a new method getInfluxUrl() spits out the final bits you need
2. A checkbox to use Basic Auth instead of Influx Auth

[tagyoureit]

Thanks @robertlabrie. Let me go through this code this week.

[tagyoureit]

Hi @robertlabrie. Thanks for submitting this PR. It looks like you've put quite a bit of work into understanding and modifying the code so kudos for that. I think I understand what you are trying to do at a high level, but the UI might be confusing me a bit.

Are there two separate logins for Nginx and then Influx? What does your "final" url look like to let you pass through the proxy to Influx?

Where you have "Enter a base url to use for Influx requests - this overrides the server settings above" this will completely replace the protocol, server and port settings?

On the Auth screen - the user selects "Use Auth" but then you added a checkbox for "Use basic auth". What exactly does this checkbox do?

Does it make more sense to have three/four different connection views?

1. Normal/basic = protocol, server port
2. Influx Auth = 1 above plus username password
3. Nginx Auth = new options with just the "Enter a base url..."
   and/or
4. Is there a combination of Nginx & Influx Auth?

thanks,
tag

[robertlabrie]

Hi Tag, Thanks for your reply. UI was never my strong suit :) So our "final" URL is https://internal-rev-proxy:443/influx/query?........ We do not use influx auth at all, that checkbox could use "Use basic auth instead of influx auth". I don't know that anyone else in the world is doing this with nginx in front of influx. I'm ok with changing the layout. One person on my team mentioned the protocol picker doesn't seem to work, I didn't check it because I was using the "baseUrl" instead. Could also add a "subdirectory" option to the connection settings, was just easier to me to paste a baseUrl in.

…

On Mon, Aug 20, 2018 at 12:27 PM tagyoureit ***@***.***> wrote: Hi @robertlabrie <https://github.com/robertlabrie>. Thanks for submitting this PR. It looks like you've put quite a bit of work into understanding and modifying the code so kudos for that. I think I understand what you are trying to do at a high level, but the UI might be confusing me a bit. Are there two separate logins for Nginx and then Influx? What does your "final" url look like to let you pass through the proxy to Influx? Where you have "Enter a base url to use for Influx requests - this overrides the server settings above" this will completely replace the protocol, server and port settings? On the Auth screen - the user selects "Use Auth" but then you added a checkbox for "Use basic auth". What exactly does this checkbox do? Does it make more sense to have three/four different connection views? 1. Normal/basic = protocol, server port 2. Influx Auth = 1 above plus username password 3. Nginx Auth = new options with just the "Enter a base url..." and/or 4. Is there a combination of Nginx & Influx Auth? thanks, tag — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEVU5QOVTqIEWynnjkMVzpuU8la4zKnRks5uSuN9gaJpZM4WCJok> .