You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/kibana-reporting-configuration.md
+4-21Lines changed: 4 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,10 @@ Before upgrading {{kib}} in a production environment, we encourage you to test y
36
36
37
37
To secure {{report-features}}, you must grant users role access to reporting functionality and protect the reporting endpoints with [API key authentication](remote-clusters/remote-clusters-api-key.md). Additionally, you can install graphical packages on the operating system to enable screenshot capabilities in the {{kib}} server.
38
38
39
-
:::{admonition} Set up security for cross-cluster search environments
40
-
TLS certificate-based authentication is deprecated in 9.0.0. To secure connections between local (self-managed) and remote clusters, set up API key authentication instead or follow a guide on how to [migrate remote clusters from certificate to API key authentication](remote-clusters/remote-clusters-api-key.md).
39
+
:::{note}
40
+
41
+
API keys are used to authenticate requests to generate reports. If you have a cross-cluster search environment and want to generate reports from remote clusters, you must have the appropriate cluster and index privileges on the remote cluster and local cluster. For example, if requests are authenticated with an API key, the API key requires certain privileges on the local cluster that contains the leader index, instead of the remote. For more information and examples, refer to [Configure roles and users for remote clusters](remote-clusters/remote-clusters-cert.md).
42
+
41
43
:::
42
44
43
45
Configuring reporting in your environment involves two main areas:
@@ -46,25 +48,6 @@ Configuring reporting in your environment involves two main areas:
46
48
47
49
Depending on your license, the type of users, and whether you prefer using the {{kib}} UI or API, there are multiple ways to [grant access to reporting functionality](#grant-user-access).
48
50
49
-
::::{admonition} Generate reports in a cross-cluster search environment
50
-
51
-
To generate reports in a cross-cluster search environment, ensure your role has the appropriate cluster and index privileges to access indices in the remote and local cluster. This may differ based on whether you are using an API key for authentication or directly authenticating as with your user credentials. For more information, refer to [Configure privileges for cross-cluster replication](remote-clusters/remote-clusters-cert.md#remote-clusters-privileges-ccr).
52
-
53
-
To provide an example, here is a role that has access to both the index in the remote cluster (`general:filebeat-*`) and the index in the local cluster (`filebeat-*`). The `read_cross_cluster` privilege allows cross-cluster search access to the remote index.
Copy file name to clipboardExpand all lines: explore-analyze/report-and-share/automating-report-generation.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,12 @@ products:
12
12
13
13
To automatically generate PDF and CSV reports, generate a POST URL, then submit an HTTP `POST` request using {{watcher}} or a script. In {{stack}} 9.1 and Serverless, you can use {{kib}} to generate reports on a recurring schedule and share them with a list of emails that you specify.
14
14
15
+
:::{note}
16
+
17
+
API keys are used to authenticate requests to generate reports. If you have a cross-cluster search environment and want to generate reports from remote clusters, you must have the appropriate cluster and index privileges on the remote cluster and local cluster. For example, if requests are authenticated with an API key, the API key requires certain privileges on the local cluster that contains the leader index, instead of the remote. For more information and examples, refer to [Configure roles and users for remote clusters](../../deploy-manage/remote-clusters/remote-clusters-cert.md).
18
+
19
+
:::
20
+
15
21
## Create a POST URL [create-a-post-url]
16
22
17
23
Create the POST URL that triggers a report to generate PDF and CSV reports.
0 commit comments