I’m trying to upgrade from elk 6.4.2 (ror 1.16.28) to 6.7.1 (ror 1.18.0). Everything works fine in 6.4.2 multi-tenant configuration with a proxy_auth configuration and nginx for authentication. Now in 6.7.1, i have ‘too many redirection’ in my browser when i’m trying to access kibana even if i see ALLOWED in elasticsearch logs for my requests.
Yes, it is supposed to work in 6.7.1 too. We’ll see why it’s not.
There might be differences in behaviour between between the plugin builds before and after 6.6.0. That’s because they are handled in different git branches.
The internal fork happened because Kibana team made a radical change of libraries in the backend and we had to rewrite most of the plugin to adapt to it.
I guess events like these bring a ton of value to our product when it comes to the classic decision maker dilemma about “is it best to buy or make your own authentication Kibana plugin?”.
Hi @FredericBallot, I tested this with the latest 1.18.1 and ES/KBN versions 7.1.1 and 6.7.1 and it works.
I attach an archive with all configuration files and the docker/makefile to reproduce it.
Hello @sscarduzio, sorry for the late reply. Everything works fine with 1.18.1 and the configuration you provided. Also, i had to export all my kibana 6.4.2 objects and reimport them in 6.7.1 to avoid the ‘too many redirections’ problem due to the space selector feature.
You know, as a ROR Enterprise user, I’d rather disable the spaces feature entirely (in kibana.yml xpack.spaces.enabled: false), as the concept of ROR tenancies greatly supersedes the concept of kibana “space”.
Not sure if anyone else has the same feeling.
What do you think?