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

[ML] Kibana landing page shows file upload link for user without ML permissions #63117

Closed
pheyos opened this issue Apr 9, 2020 · 6 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience :ml REASSIGN from Team:Core UI Deprecated label for old Core UI team

Comments

@pheyos
Copy link
Member

pheyos commented Apr 9, 2020

Falls into same category as #21017

Found in version

  • 7.7.0-bc5

Browser

  • Chrome

Steps to reproduce

  • Log into Kibana without any ML permissions

Expected result

  • The Kibana landing page doesn't contain any links to ML

Actual result

  • The ML app link is removed correctly, but the Import a CSV, NDJSON, or log file link is still there:
    kibana_landing_page_without_ml_permissions

Additional information

  • Following that link leads to a 404 page, which is the expected behavior with missing permissions
@pheyos pheyos added bug Fixes for quality problems that affect the customer experience :ml v7.7.1 labels Apr 9, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@jgowdyelastic
Copy link
Member

I believe this fix needs to happen in the EnvironmentService in the home plugin.
In the same way we register ML for the feature catalogue, we don't control whether the link should be shown.
Perhaps @flash1293 could have some input here?

@flash1293
Copy link
Contributor

I looked into the issue and it looks like for now the home app should take care of this.

For the app links this filter takes care of removing the reference if the user is not allowed to access:

.filter(entry => capabilities.catalogue[entry.id] !== false)

For the environment this is not happening (but it could in the same way - check the capabilities and set ml to false if the current user is not allowed to access it):

const mlEnabled = environment.ml;

@elastic/kibana-core-ui Seems like a good first issue to get started with "Home" development - do you want to take over?

@ryankeairns
Copy link
Contributor

@flash1293 we'll take a look at this for 7.7.1. During our weekly sync, @bmcconaghy noted some other longer term changes that we'd like to make here as well (e.g. turning this around so the plugin is doing the work to determine if the link should appear, etc.).

We're currently solely focused on the nav work, so this will likely not get touched for a couple of weeks. Let us know if that becomes a problem.

@ryankeairns
Copy link
Contributor

Falls into the same category as #21017

@ryankeairns
Copy link
Contributor

Addressed by new home page.

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 :ml REASSIGN from Team:Core UI Deprecated label for old Core UI team
Projects
None yet
Development

No branches or pull requests

6 participants