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

Reporting - Management Access Denied page #18284

Closed
elasticmachine opened this issue Jun 22, 2017 · 4 comments
Closed

Reporting - Management Access Denied page #18284

elasticmachine opened this issue Jun 22, 2017 · 4 comments
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result 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

Comments

@elasticmachine
Copy link
Contributor

Original comment by @kobelb:

When a user isn't authorized to use Reporting, when they go to the Management page, there are just no reports listed. This doesn't make it immediately obvious to the user that they aren't authorized.

The following is what Monitoring is doing if you aren't authorized:

screen shot 2017-06-22 at 8 25 45 am

@elasticmachine elasticmachine added :Sharing (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels Apr 25, 2018
@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed :Sharing labels Sep 13, 2018
@tsullivan tsullivan added release_note:enhancement enhancement New value added to drive a business result and removed release_note:enhancement labels Jan 24, 2019
@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 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 Author

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

@tsullivan
Copy link
Member

@epixa wrote a comment that is relevant here: #19914 (comment)

I think the solution here is to base reporting’s security perms off of the new application privileges model rather than continuing to rely on this role config. Then you’d get UI/API based control over this for free.

What we need is UI based control backed by the user permissions.

Closing for #21689

@elasticmachine
Copy link
Contributor Author

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

@tsullivan
Copy link
Member

Oops, forgot to click "Close"

What we need is UI based control backed by the user permissions.

This was completed in #94966 (7.14)

@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 May 13, 2021
@sophiec20 sophiec20 added the Feature:Reporting:Framework Reporting issues pertaining to the overall framework label 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
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result 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
Projects
None yet
Development

No branches or pull requests

6 participants