search

fangli / kibana-authentication-proxy

Hosts the latest kibana3 and elasticsearch behind Google OAuth2, Basic Authentication or CAS Authentication
MIT License
223 stars 66 forks source link

kibana shows blank page with error #41

Open maxhyjal opened 9 years ago

maxhyjal commented 9 years ago

After following the installation procedure and starting nodejs app. It prompted me to enter the password(using basic auth). But after I enter the correct password, I'm getting a blank page with Cannot GET / error.

Is there some step I'm not aware of during the configurations?

Thanks!

bof64665 commented 9 years ago

I'm running into the same issue using Basic Auth. The blank page with Cannot GET/ - error is displayed in Chrome. IE displays a site saying that it run into a 404-error. Authorization is working as it should, because entering the wrong password leads to a blank page saying "unauthorized".

Would be nice if some could get this fixed or even tell me and maxhyjal what we're doing wrong.

mungeol commented 9 years ago

Same problem here.

Blendwolf commented 9 years ago

So I got the same error. The problem lies in the newest version of kibana. If you chose not to update the built in kibana, the authentication works perfectly fine.

johnnybraga commented 9 years ago

Same problem here. Any fix besides not update kibana?

ghost commented 9 years ago

Any updates?

faxm0dem commented 9 years ago

are you guys using this against ES 1.4.x?

spyzzz commented 9 years ago

Got the same issues, someone fixed it ?

bof64665 commented 9 years ago

There are no updates made to face this issue. For me it worked not to update the kibana version. So the solution from blendwolf seems to be the only one.

izhan commented 9 years ago

Confirmed here as well. Any workaround for Kibana 4 would be appreciated!

noamgal commented 9 years ago

Looks like the fix is not in master yet, I just git clone https://github.com/izhan/kibana-authentication-proxy.git and got this commit: commit 304b944b354f158a18cc584055df635cbb4f5b26 Author: Irvin Zhan <izhan@princeton.edu> Date: Thu Dec 18 09:23:07 2014 -0500 configure to allow for google oauth and didn't get GET / error

izhan commented 9 years ago

ah yes, my fork you mentioned used a reverse proxy built in express to workaround this. there are a few more commits that aren't pushed up to that fork that addresses some issues with it. i can push it up when i have a chance.

we ultimately switched to a simple nginx proxy. the fork had some issues due to a bug in kibana parsing, though that issue might have been fixed in kibana master already.

hmalphettes commented 9 years ago

@izhan support for Kibana 4 is unlikely to be possible on a reverse proxy like this. Kibana 4 requires its own web tier as explained here: https://github.com/elasticsearch/kibana/issues/1628#issuecomment-58611294

@fangli may I suggest a small explanation in the Readme like this one: https://github.com/hmalphettes/kibana-proxy/commit/f3e9d254dea35ddb15d5e34ae2eb7e5cc9293c24