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

[Request][Fleet] Account for removal of superuser requirement to access UI #1488

Closed
jen-huang opened this issue Jan 24, 2022 · 4 comments · Fixed by #1645
Closed

[Request][Fleet] Account for removal of superuser requirement to access UI #1488

jen-huang opened this issue Jan 24, 2022 · 4 comments · Fixed by #1645
Assignees
Labels
Team:Docs Label for the Observability docs team Team:Fleet Label for the Fleet team v8.1.0

Comments

@jen-huang
Copy link
Contributor

Description

Account for removal of superuser requirement to access UI, as implemented in 8.1 via elastic/kibana#108252.

At minimum this page:
https://www.elastic.co/guide/en/fleet/current/install-fleet-managed-elastic-agent.html

Collaboration

  • The docs team will lead producing the content

Contact Person: @criamico

Suggested Target Release

8.1

Stakeholders

Fleet UI team

@jen-huang jen-huang added Team:Docs Label for the Observability docs team Team:Fleet Label for the Fleet team labels Jan 24, 2022
@joshdover
Copy link
Contributor

We also should update the relevant row in the Beats v Agent comparison table here: https://www.elastic.co/guide/en/fleet/current/beats-agent-comparison.html

@mostlyjason
Copy link
Contributor

mostlyjason commented Feb 9, 2022

@joshdover can we also document the privileges users need to use Fleet & Elastic Agent? I'm thinking something equivalent to https://www.elastic.co/guide/en/beats/filebeat/7.16/feature-roles.html. In addition to the Kibana privileges Fleet and Integrations, they also need Kibana privileges for Dashboards. They also need index privileges for common data streams, particularly elastic_agent data streams. They may also need a privilege for the Fleet Server service token. Dede might need some guidance on what these should be.

@dikshachauhan-qasource
Copy link

Hi @jen-huang

We have validated the related links for the docs changes and our observations are shared below:

  1. https://www.elastic.co/guide/en/fleet/current/install-fleet-managed-elastic-agent.html
  • Changes reflected properly under Privileges section :
    "Kibana user with All privileges on Fleet and Integrations. Since many Integrations assets are shared across spaces, users need the Kibana privileges in all spaces."
  1. https://www.elastic.co/guide/en/fleet/current/beats-agent-comparison.html
  • Allow non-superusers to manage assets and agents section is updated with required info as per mentioned under file changed.
  1. https://www.elastic.co/guide/en/beats/filebeat/7.16/feature-roles.html
  • No updates were observed at above page for fleet access requirements.

@dedemorton can you please confirm changes to validate on above page.

Thanks
QAS

@dedemorton
Copy link
Contributor

I'm not sure why item 3 is on this list. We do not document Fleet in the Beats documentation. The other links look right. thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Docs Label for the Observability docs team Team:Fleet Label for the Fleet team v8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants