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

Enable PDF reporting with dashboard read only feature control #41407

Closed
nreese opened this issue Jul 17, 2019 · 6 comments
Closed

Enable PDF reporting with dashboard read only feature control #41407

nreese opened this issue Jul 17, 2019 · 6 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

@nreese
Copy link
Contributor

nreese commented Jul 17, 2019

There is currently no way to have a dashboard read only role that also has reporting capabilities.

kibana_dashboard_only_user role does not provide PDF reporting sharing options even if the user also the roles kibana_user and reporting_user.

A custom role with Kibana privileges restricting dashboard to read only does not work either. Reporting requires kibana_user role which provides access to all features.

When you assign a user multiple roles, the user receives a union of the roles’ privileges. Therefore, assigning the kibana_user role in addition to a custom role that grants Kibana privileges is ineffective because kibana_user has access to all the features in all spaces. https://www.elastic.co/guide/en/kibana/current/xpack-security-authorization.html

@nreese nreese added enhancement New value added to drive a business result (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Stack Services labels Jul 17, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services

@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)

@ivssh
Copy link

ivssh commented Dec 10, 2020

+1 for this.
Any updates on if this will be supported?

@elasticmachine
Copy link
Contributor

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

@tsullivan
Copy link
Member

As of #94966, access to Reporting features can be customized using custom Kibana app privileges. This allows users that do not have the kibana_user role to use Reporting.

Allowing read-only users to create reports will inherently be fixed by #99890

@tsullivan
Copy link
Member

Closing in favor of #99890

@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 Jun 1, 2021
@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (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
(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

7 participants