Upgrading from 1.26.1 to 1.30.1 logged out issue (enterprise)


I encountered issue after upgrading RoR from 1.26.1 to 1.30.1, my kibana stopped to working correctly, i can log in, but after 5 sec i will recieve a logged out message.

There are nothing wrong with logs, all the request are allowed, i can brwoser the kibana and execute everything in devtools, but i will get disconnected if i lose focus to the kibana.

There are some proofs, notice the old version info in kibana app.

BTW are you supporting some interactive sessions with Enterprise customers? e.g. screen share to show you the issues?

Can you explain what is happening?



elasticsearch-data-04   readonlyrest      1.30.1
elasticsearch-data-01   readonlyrest      1.30.1
elasticsearch-data-03   readonlyrest      1.30.1
elasticsearch-data-02   readonlyrest      1.30.1
elasticsearch-client-01 readonlyrest      1.30.1
elasticsearch-master-01 readonlyrest      1.30.1

./kibana-plugin list

[email protected]

cat package.json

  "name": "readonlyrest_kbn",
  "version": "1.30.1",
  "ror_version": "enterprise-1.30.1_es7.7.1",
  "ror_build_time": "Wed, 26 May 2021 18:05:51 GMT",
  "ror_valid_for_days": "99999",
  "license": "Beshu Limited, All rights reserved",
  "private": true,
  "description": "ReadonlyREST security plugin for Elasticsearch and Kibana",
  "main": "index.js",
  "kibana": {
    "version": "7.7.1"
  "dependencies": {
    "@babel/runtime": "^7.9.2",
    "@types/classnames": "^2.2.10",
    "@types/react": "^16.9.35",
    "@types/react-dom": "^16.9.8",
    "axios": "^0.21.1",
    "boom": "^7.1.1",
    "brace": "^0.10.0",
    "classnames": "^2.2.6",
    "cookie-parser": "~1.4.4",
    "crypto-js": "^4.0.0",
    "express": "~4.16.1",
    "express-session": "^1.15.6",
    "grant-hapi": "^4.6.1",
    "hapi": "^17.5.3",
    "hapi-auth-cookie": "9.1.0",
    "http-errors": "~1.6.3",
    "joi": "^10.2.2",
    "jsonwebtoken": "^8.3.0",
    "lodash": "4.17.15",
    "openid-client": "^3.14.0",
    "passport": "^0.4.0",
    "passport-openidconnect": "0.0.2",
    "passport-saml": "^1.3.3",
    "quick-lru": "^4.0.1",
    "react": "^16.13.1",
    "react-dom": "16.13.1",
    "replace-prefix": "^0.0.1",
    "typescript": "^3.8.3",
    "uuid": "^3.0.1",
    "yamljs": "^0.2.9",
    "yar": "^9.1.0"


Can you see the browser’s console logs? Any reference to session probe when you are booted out?

If yes, can you hit preserve log in Chrome network tab (dev console, ctrl+shift+c) and see what happens to the AJAX call to “/session-continuity-check” ?

Yes I actually enjoy connecting with customers using calls or video calls. Sometimes it can unlock the comprehension of a support issue quite rapidly, or anyways it can end up as an interesting exchange shedding some light on how the product is perceived and what are the current biggest pain points.

There was no call in regards of /session-continuity-check, i can double check.

That is great, for us it will be better to do the session, because we have big cluster and lot of configuraiton that is hard to share everything there on the forum.

How we can schedule the meetings or contact you if we want to schedule the interactive sessions ?

There is screenshot from devtools network tab

OK maybe I know: try clearing browser’s cache?

its happening even in incognito, so cache or cookies are cleared.


Just for others, who use google.

If you have similar issue, please remove all content in optimize folder, its located in root folder of kibana instalation, then start again kibana, it will load slowly for first time, but issue will be gone.

Thanks @sscarduzio for the call!

@Sinedko thanks for being so thoughtful to update the thread :pray:

In the meantime, I updated the docs too.