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.

Sign up for GitHub

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

Jump to bottom

Remove full-page refresh after logging in #75077

Open
joshdover opened this issue Aug 14, 2020 · 4 comments
Open

Remove full-page refresh after logging in #75077

joshdover opened this issue Aug 14, 2020 · 4 comments
Labels
blocked Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
Kibana developer experience [NOTICE T...

Comments

@joshdover
Copy link
Contributor

Currently, we do a full page refresh after a user logs in successfully. In order to improve the perceived performance of Kibana, we should move to using a core.application.navigateToUrl API call to trigger an SPA navigation.

The major blocker to doing this is adding support for dynamic UI capabilities #59377.

There is also a related issue for removing the full page refresh from the space selector: #59555
@joshdover joshdover added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! labels Aug 14, 2020
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@mshustov mshustov mentioned this issue Aug 14, 2020
Closed
29 tasks
@mshustov
Copy link
Contributor

Before implementing this, we need to add functional tests to make sure logout and session expired events reload Kibana to reset in-memory user data.

@joshdover
Copy link
Contributor Author

FYI the feature usage registration calls on the client-side will need to be buffered before this is implemented: #77411

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Aug 5, 2021
@legrego legrego added loe:needs-research This issue requires some research before it can be worked on or estimated and removed loe:small Small Level of Effort labels Oct 6, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:small Small Level of Effort and removed loe:needs-research This issue requires some research before it can be worked on or estimated labels Feb 14, 2022
@legrego legrego removed EnableJiraSync loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
No open projects
Kibana developer experience [NOTICE T...
Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@joshdover @mshustov @legrego @elasticmachine