Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LoginApp not shown if kibana is deployed with a base path starting with /app #67690

Closed
g-w opened this issue May 28, 2020 · 7 comments
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@g-w
Copy link

g-w commented May 28, 2020

Kibana version:
7.7.0
Elasticsearch version:
7.7.0
Server OS version:
Debian 10
Browser version:
Firefox / Google Chrome
Browser OS version:
Fedora
Original install method (e.g. download page, yum, from source, etc.):
Docker image
Describe the bug:
If kibana is configured to use a server.basePath starting with /app (ie. /apps/kibana) the LoginApp provided by the security plugin is not shown.
Steps to reproduce:

  1. Install elastic search with a security configuration
  2. Configure kibana with server.basePath: /apps/kibana
  3. Visit /apps/kibana

Expected behavior:
The login form shows.

Any additional context:
This issue is related to https://github.com/elastic/kibana/blob/7.7/src/core/public/application/ui/app_router.tsx#L59 . Here the mounter.appBasePath is checked which contains the base path of the application ie. /apps/kibana/login. Hence no route is drawn and the login form not shows.

@majagrubic
Copy link
Contributor

majagrubic commented May 29, 2020

Hi @g-w, thanks for reporting this issue.

@majagrubic majagrubic added triage_needed Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels May 29, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@joshdover
Copy link
Contributor

@pgayvallet do you know if this is resolved by any of the fixes you've done in this area recently?

@pgayvallet
Copy link
Contributor

This is resolved by #65977 + #67125 in 7.9+

Should I backport them to 7.7 / 7.8 ?

@joshdover
Copy link
Contributor

Should I backport them to 7.7 / 7.8 ?

Yep, let's do that.

@pgayvallet
Copy link
Contributor

pgayvallet commented Jun 3, 2020

#65977:
7.8: #68072
7.7: #68073

#67125:
7.8: #68089
7.7: #68090

@pgayvallet pgayvallet added bug Fixes for quality problems that affect the customer experience and removed triage_needed labels Jun 3, 2020
@pgayvallet
Copy link
Contributor

Will be fixed in 7.7.1 and 7.8.0+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

5 participants