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

[Fleet] Switch to kibana_system user for setup & all package operations #111755

Closed
Tracked by #111858 ...
joshdover opened this issue Sep 9, 2021 · 1 comment · Fixed by #112808
Closed
Tracked by #111858 ...

[Fleet] Switch to kibana_system user for setup & all package operations #111755

joshdover opened this issue Sep 9, 2021 · 1 comment · Fixed by #112808
Assignees
Labels
enhancement New value added to drive a business result required-for-8.0 This work is required to be done before 8.0 lands, bc it relates to a breaking change or similar. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@joshdover
Copy link
Contributor

Blocked by elastic/elasticsearch#77294

In order to facilitate automatic setup and package upgrades on Kibana startup, we need to be switch all of our API calls to Elasticsearch and Saved Objects to use the internal kibana_system user instead of the user that calls the setup API.

We should still require superuser and Fleet Kibana privileges to install packages or call the setup API for the time being.

@joshdover joshdover added enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team labels Sep 9, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result required-for-8.0 This work is required to be done before 8.0 lands, bc it relates to a breaking change or similar. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants