Hi,
I’ve found some difference between the working setup and the setup that is throwing this error.
│ 192.168.10.39 ──https─► 192.168.10.80
├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│POST /app/kibana/api/v1/auth/login HTTP/1.1
│Host: host10dot80c.server35.lab
│User-agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
│Accept: application/json, text/plain, /
│Accept-Language: en-US,en;q=0.9
│Accept-Encoding: gzip, deflate, br
│Connection: keep-alive
│Origin: https://host10dot80c.server35.lab
│Content-Type: application/json;charset=UTF-8
│Content-Length: 50
│
│{
│ “password” : “Password1”,
│ “username” : “kibanaadmin”
│}
``
Shown above is the login request from the setup where I’m facing this issue and as you can see that there is no cookie field.
Login request shown below is from the working setup and it has a cookie field.
│ 192.168.10.39 ──https─► 192.168.10.51
``
├─────────────────────────────────────────────────────────────────────────────────────────────────────
│POST /app/kibana/api/v1/auth/login HTTP/1.1
│Host: host10dot51c.server36.lab
│User-agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
│
│Accept: application/json, text/plain, /
│Accept-Language: en-US,en;q=0.9
│Accept-Encoding: gzip, deflate, br
│**Cookie: JSESSIONID=0000ApvHwDtXcCbc2O0KUhKo_8H:-1 **
│Connection: keep-alive
│Origin: https://host10dot51c.server36.lab
│Content-Type: application/json;charset=UTF-8
│Content-Length: 50
│
│{
│ “password” : “Password1”,
│ “username” : “kibanaadmin”
│}
Is the missing cookie resulting in this Error? Also why is the Cookie field missing on that particular setup?
···
On Tuesday, July 31, 2018 at 7:50:54 PM UTC+5:30, ihjaz Mohamed wrote:
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
SearchGuard 6 - 6.2.2-21
Search-guard-kibana-plugin-6.2.2-10
Elasticsearch & Kibana - 6.2.2
- Installed and used enterprise modules, if any
none
- JVM version and operating system version
OpenJDK Runtime Environment (build 1.8.0_161-b14)
OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)
Red Hat Enterprise Linux Server release 7.4 (Maipo)
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
Hi,
I have multiple Kibana instances with Kibana Searchguard plugin load balanced over Nginx.
I get the following error when I try to login to Kibana from the Searchguard login page.
Error: Uncaught TypeError: Super expression must either be null or a function, not undefined (https://elite10dot80c.elite35.lab/app/kibana/bundles/vendors.bundle.js?v=16588:89)
at window.onerror (https://elite10dot80c.elite35.lab/app/kibana/bundles/commons.bundle.js?v=16588:1:506240)
``
If I enable session affinity on the Nginx then I don’t see this issue but I need to keep the session affinity disabled on the Nginx for my solution.
Also I see this only on one of the cluster in my lab while other clusters with the same solution do not have this issue.
So does Kibana Searchguard plugin require affinity or stickiness to be enabled on the load balancer? Or is there anything else I’m missing here as this issue is not seen on other clusters with affinity disabled?
