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

User doesn't see any message and cannot click on reporting tab if she is on expired license #36281

Closed
bhavyarm opened this issue May 8, 2019 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Reporting:Framework Reporting issues pertaining to the overall framework 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 needs-team Issues missing a team label regression

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented May 8, 2019

Kibana version: 7.1.0 BC2

Elasticsearch version: 7.1.0 BC2

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: If user is on expired trial license - she can't click on reporting tab neither does the Kibana UI display why she cannot.

Earlier reporting tab would display your license was expired. Not sure when the regression happened. Also this might be a good time to consider if we want user to open the reporting tab and then display the license expired message or show the reports which got generated before the license expired. Right now after the fall back to basic - the csv reports are gone too.

cc @joelgriffith @AlonaNadler

can't_click_reporting

@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience regression (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Visualizations Visualization editors, elastic-charts and infrastructure labels May 8, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@tsullivan tsullivan self-assigned this Jul 8, 2019
@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@tsullivan tsullivan removed their assignment Sep 30, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bmcconaghy bmcconaghy added Team:Reporting Services and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@tsullivan tsullivan added Team:Reporting Services loe:medium Medium Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Feb 25, 2021
@tsullivan
Copy link
Member

I have not had a chance to re-test this, but @elastic/kibana-security @elastic/kibana-core in theory, is this issue resolved #94966 now that Reporting uses feature controls?

I believe one of the integration fields with feature controls was the license type, which suggests that feature controls limits access by custom role and the state of the license.

@legrego
Copy link
Member

legrego commented May 14, 2021

Feature Controls only integrates with licensing to know which options to make available in the Role Management UI when configuring permissions. We do not control access to features based on the current license: that is not within the scope of the security system, and is something that has always been deferred to plugins to take care of.

We will hide the Reporting tab for unauthorized users, but the reporting plugin should be doing its own licensing checks

@exalate-issue-sync exalate-issue-sync bot added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Jun 3, 2021
@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. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Aug 20, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:small Small Level of Effort and removed loe:medium Medium Level of Effort labels Nov 22, 2021
@ppisljar
Copy link
Member

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@ppisljar ppisljar closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2022
@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
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 Feature:Reporting:Framework Reporting issues pertaining to the overall framework 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 needs-team Issues missing a team label regression
Projects
None yet
Development

No branches or pull requests

9 participants