Its possible to use IIS with the following steps. 1) Disable Output cache for the website you are using as reverse proxy. 2) Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy. On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman wrote: > > We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for > auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace > Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed > directly, but we need authentication and whatever I do I cannot make it > work from behind reverse proxy! Early or later I get 401 accessing some > internal resource. > > Wonder if anybody hit similar problem and have any insight how to make it > work. > We cannot use Shield as its price is way beyond our bounds. > > Thanks! > Konstantin -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7355f0ec-1bac-4e62-b675-a5f23d04ef7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
