Hello @mgopathi01 ,
You can use this Docker image for testing beshultd/kibana-readonlyrest-dev:7.17.24-ror-1.69.0-pre1purpose
Hello @Dzuming,Thank you for the build !
I’m noticing a potential issue after the upgrade related to multi-tab tenancy behavior, and I wanted to check if you can reproduce it on your side.
Scenario:Per tab tenancy
-
Open Tab 1, select Tenant A, and run a search.
→ Results are correct (Tenant A has access to indexsales). -
Duplicate Tab 1 to create Tab 2.
-
In Tab 2, switch the tenancy to Tenant B and run a search.
→ Results are correct (Tenant B has access to indexmarket). -
Now switch back to Tab 1 (which still visually shows Tenant A).
Observed behavior:
-
Even though Tab 1 still displays Tenant A as the selected tenancy, the search results appear to behave as if Tenant B is applied.
-
It looks like the tenancy context from Tab 2 is leaking into Tab 1 after the tab switch.
To make it concrete, could you try testing with:
-
Tenant A → access to index
sales -
Tenant B → access to index
market
and follow the steps above to see if the same behavior occurs?
Let me know if this matches what you see, happy to provide more details if needed.
Link Sharing :
I see it doesn’t work ,i just get blank page for example the url i copy looks like
“https://example.com/s/default/goto/9ce96460-f577-11f0-8035-d3c5ee395beb”
and when i copy url in new tab it changes to below but with blank page
Could you also test this case from your side.
Hello @mgopathi01
Thanks for testing!
Scenario:Per tab tenancy
I tried to reproduce it on my side, but with no success yet. Could you verify if my steps to reproduce are correct? video
Link Sharing :
For some reason, your URL includes https://example.coms/s/, which is a wrong URL. I was able to reproduce the blank page issue on your Kibana version, but differently, I copied a link to a Discover for Tenancy B, opened a new browser, and pasted the copied link, and I got a 404 error from a short_url request.
I will provide a new pre-release build with a fix of this 404 not found issue
@Dzuming It looks like i dont have access to video url ,could you provide access.
@Dzuming It looks like i dont have access to video url ,could you provide access.
Also, I provided a new pre-release image beshultd/kibana-readonlyrest-dev:7.17.23-ror-1.69.0-pre2. Let me know if it resolves the second problem on your side.
Hello @Dzuming Apologies for delay ,since i am on vacation ,please expect some delay in response could you share version 7.17.24 or 8.17.1 thanks !
Hello @mgopathi01
Hello @Dzuming Apologies for delay ,since i am on vacation ,please expect some delay in response could you share version 7.17.24 or 8.17.1 thanks !
No problem! Here is a Docker image for Kibana 7.17.24 beshultd/kibana-readonlyrest-dev:7.17.24-ror-1.69.0-pre2
Hello @Dzuming ,Thank you for new build ! ,i see now short url works fine but for some reason still per tab tenancy doesnt work as expected ,i have shared recording over email ,could you take a look.
Hello @mgopathi01
Thanks for the reproducer. I’m taking a look at it.
Hello @mgopathi01
I prepared a new image with a fix of the issue Scenario:Per tab tenancy
beshultd/kibana-readonlyrest-dev:7.17.24-ror-1.69.0-pre3
@Dzuming ,Thank you for the build ,when i tried to switch tenant i get below error in kibana logs.
Let me know if more details are required.
{“type”:“response”,“@timestamp”:“2026-01-26T11:51:42+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:404,“req”:{“url”:"/switch-group?group=XX_RW&redirectTo=https%3A%2F%``example.com``%2Fs%
Error: Cannot remove headers after they are sent to the client
full log :
{“type”:“response”,“@timestamp”:“2026-01-26T11:51:42+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:404,“req”:{“url”:“/switch-group?group=XX_RW&redirectTo=https%3A%2F%``example.com``%2Fs% │
│ Error: Cannot remove headers after they are sent to the client │
│ at ServerResponse.removeHeader (node:_http_outgoing:808:11) │
│ at clearAllHeaders (/usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserResHeaders.js:14:11) │
│ at /usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserResHeaders.js:22:9 │
│ at new Promise () │
│ at /usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserResHeaders.js:21:14 │
│ at processTicksAndRejections (node:internal/process/task_queues:95:5) │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:42+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/app/discover?tenancy=U2FsdGVkX1%2Fu0o%2FNbr8gxtUwvnNh%2Fut1et3N9rxvtR3LgjxiSXOHKyHg │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:42+00:00”,“tags”:[“api”],“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/api/status”,“method”:“get”,“headers”:{“host”:“localhost:5601”,“user-agent”:“cu │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:42+00:00”,“tags”:[“api”],“pid”:31,“method”:“get”,“statusCode”:304,“req”:{“url”:“/bootstrap.js”,“method”:“get”,“headers”:{“host”:“``example.com``”, │
│ {“type”:“response”,“@timestamp”:“2026-01-26T11:51:43+00:00”,“tags”:,“pid”:31,“method”:“post”,“statusCode”:200,“req”:{“url”:“/api/core/capabilities”,“method”:“post”,“headers”:{“host”:“``example.com`` │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:43+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/internal/security/me”,“method”:“get”,“headers”:{“host”:“``example.com`` │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:43+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:204,“req”:{“url”:“/internal/security/session”,“method”:“get”,“headers”:{“host”:“``kexample.com`` │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:43+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/api/banners/info”,“method”:“get”,“headers”:{“host”:“``example.com``”," │
│ {“type”:“response”,“@timestamp”:“2026-01-26T11:51:43+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/internal/spaces/_active_space”,“method”:“get”,“headers”:{“host”:“``example.com`` │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:44+00:00”,“tags”:,“pid”:31,“method”:“get”,“statusCode”:404,“req”:{“url”:“/api/index_patterns/_fields_for_wildcard?pattern=index-pattern* │
│ Error: userResDecorator should return string or buffer as data │
│ at verifyBuffer (/usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserRes.js:34:19) │
│ at /usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserRes.js:74:9 │
│ at new Promise () │
│ at /usr/share/kibana/plugins/readonlyrestkbn/node_modules/express-http-proxy/app/steps/decorateUserRes.js:72:14 │
│ at processTicksAndRejections (node:internal/process/task_queues:95:5) │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:51:52+00:00”,“tags”:[“api”],“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/api/status”,“method”:“get”,“headers”:{“host”:“localhost:5601”,“user-agent”:“cu │
│ {“type”:“response”,”@timestamp":“2026-01-26T11:52:02+00:00”,“tags”:[“api”],“pid”:31,“method”:“get”,“statusCode”:200,“req”:{“url”:“/api/status”,“method”:“get”,“headers”:{“host”:“localhost:5601”,“user-agent”:"cu │
│ │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Thank you for the build ,when i tried to switch tenant i get below error in kibana logs.
Is it something blocking you from changing tenancy, or just an error in the logs? I saw this error during my testing, but since it was possible to change a group, I left it for later. But maybe it’s a different case on your side?.
Its blocking from switching tenants and at same time i see mentioned error in logs.
i have sent screen recording over email ,could you take a look.
Hello @mgopathi01
I prepared a new pre-release image with a fix of the above error beshultd/kibana-readonlyrest-dev:7.17.24-ror-1.69.0-pre4
1 Like
Hello @Dzuming ,Thank you for the build on quick test both features , per tab tenancy and short url works fine.
2 Likes
Hello @Dzuming ,Could you let me know when will be official build released.
Thank you !
Hi @mgopathi01
We are preparing to release ROR 1.69.0.
We should be ready to do it within 2 weeks or so (we’re in a middle of implementation of one important change).
1 Like
Hello @coutoPL ,Could you please let me know if its going to take more time for official build.
Hi @mgopathi01
Yes, we need some more time, but we are closing last two tasks that have to be a part of this release. I remember about you and I will let you know. We should be ready for the release in the next week.
Thank you @coutoPL