Closed drewdaemon closed 3 weeks ago
Pinging @elastic/kibana-security (Team:Security)
Hey @drewdaemon, thanks for filing the issue! I believe what you're experiencing is described in https://github.com/elastic/kibana/issues/83914 (see Multi-tenancy using the same host name, but different ports
). If so, then everything is working as intended, even though it’s definitely confusing (HTTP state spec 🤷). If you'd like to run multiple Kibanas on the same host, you'll need to use different cookies. Here's an example if you'd like to run multiple Kibana instances locally on different ports:
# Terminal #1
yarn start (implies `--server.port=5601 --dev.basePathProxyTarget=5603 --xpack.security.cookieName=sid`)
# Terminal #2
yarn start --server.port=5701 --dev.basePathProxyTarget=5703 --xpack.security.cookieName=sid7
I'm closing the issue, but feel free to re-open it if my guess is wrong.
Okay, thanks for checking @azasypkin !
Describe the bug:
Steps to reproduce:
yarn start
(different ports can be configured withserver.port
inkibana.yml
)kibana.yml
(server.basepath
should be missing!)Result: you're logged out of Kibana 1.
Server log:
It appears to fail this validation: https://github.com/elastic/kibana/blob/3ae4111a77bc558c478e42da0e6803a901ec27c9/x-pack/plugins/security/server/session_management/session_cookie.ts#L91-L101
If the base paths are explicitly set in
kibana.yml
, the problem isn't present.