302

[windowsrefund]

Hello and thanks for this. I'll describe my setup:

Both logs.example.com and search.example.com are served via an nginx proxy. Each service resides on its own node behind the proxy. I can GET from elasticsearch as expected and if I run Kibana on port 80, all is good.

I stopped Kibana (nginx) and am attempting to use kibana3_auth instead. Followed the instructions in issue #19 and starting the rack instance on port 80

kibana/src/config.js contains: elasticsearch: "http://search.example.com:9200"

config/config.rb contains: :backend => "http://search.example.com:9200"

Problem 1: Pointing my browser to logs.example.com does not result in a redirect to logs.example.com/login

So now I add the path manually

Problem 2: Now I can login (yay!) but nothing happens. On the rack side, I see this 302:

$forwarded_for - - [18/Aug/2014 17:08:08] "POST /login HTTP/1.1" 302 - 0.0024

I suspect this may be related to the proxy but could use some help.

[christian-marie]

Try looking at the raw response, it sounds like it is forwarding a 302, which is probably odd.

[windowsrefund]

I don't see anything odd in my capture but wanted to ask if anyone has run this successfully behind a proxy? It's also interesting to see how this use case has a PR waiting for a similar project

https://github.com/fangli/kibana-authentication-proxy/pull/20

[christian-marie]

Looks plausible, you could certainly give that same approach a go.