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 telemetry to indicate how many one-time reports are using user credentials instead of API keys #217166

Open
3 tasks
mikecote opened this issue Apr 4, 2025 · 1 comment
Labels
Feature:Reporting:Framework Reporting issues pertaining to the overall framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Apr 4, 2025

Once https://github.com/elastic/kibana-team/issues/1331 is implemented, reports should mainly use API keys as the authentication method. However, there are some situations where a fallback mechanism will still be needed where it uses the user credentials:

  • API keys are disabled in Elasticsearch xpack.security.authc.api_key.enabled
  • The Kibana Encrypted saved-objects plugin is using a generated encryption key

In those situations, the report will use the user credentials to authenticate the report. We should track how often this happens so we know when we can make a breaking change and stop supporting one-time reports in such situations.

Definition of Done

  • We can get a count of times a cluster used user credentials to generate a report
  • We can get a count of clusters that are still using user credentials
  • Tests
@mikecote mikecote added Feature:Reporting:Framework Reporting issues pertaining to the overall framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 4, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Reporting:Framework Reporting issues pertaining to the overall framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants