-
Notifications
You must be signed in to change notification settings - Fork 163
[DOCS][ResponseOps][Reporting][9.1 & Serv] Add documentation about required privileges with API key authentication #2885
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
Merged
+10
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Preview links for changed docs |
ymao1
approved these changes
Oct 21, 2025
mdbirnstiehl
approved these changes
Oct 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦭 👍
florent-leborgne
approved these changes
Oct 21, 2025
wajihaparvez
approved these changes
Oct 21, 2025
nastasha-solomon
added a commit
to elastic/kibana
that referenced
this pull request
Oct 21, 2025
… privileges with API key authentication (#234255) Contributes to elastic/docs-content#2679 by adding a note about the new API authentication key method that was implemented for report generation in 8.19. The note also explains the specific cluster and index privileges that users with cross-cluster search environments must have. Previews: - [Automatically generate reports](https://kibana_bk_234255.docs-preview.app.elstc.co/guide/en/kibana/8.19/automating-report-generation.html) - [Configure reporting in Kibana](https://kibana_bk_234255.docs-preview.app.elstc.co/guide/en/kibana/8.19/secure-reporting.html) **Corresponding 9.x/Serverless doc updates:** elastic/docs-content#2885
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributes to #2679 by adding a note about the new API authentication key method that was implemented for report generation in 8.19. The note also explains the specific cluster and index privileges that users with cross-cluster search environments must have.
Previews:
Corresponding 8.19 doc updates: elastic/kibana#234255