I've encountered another redirect loop, not sure if it's the same one that you were referring to encountering internally.
As I mentioned, I'm routing to multiple Kibana instances from a single URL based on the context.
I can login fine to
kibana.contoso.com/foo/ and get the
sid cookie on the path of
I can then immediately login to
kibana.contoso.com/ and get it's own
sid cookie on path of
But if I login to
kibana.contoso.com/ first and get the cookie, and then proceed to login to
kibana.contoso.com/foo/ I get stuck in a redirect loop. Since I now see the cookie at path
/, I'm guessing that's causing some type of conflict? Simply deleting the
sid cookie from
/ allows me to login fine.
It's worth mentioning that both Kibana instances have the same
shield.encryptionKey value. More of an oversight when creating the second instance, I'm assuming they should be different?
If I change the
shield.encryptionKey value on the
/foo/ instance, I simply get redirected back to the login page to enter credentials, not stuck in a loop. I can see the request header submitting the cookie from
/ and getting a response back setting an expired, empty
sid cookie on path