Skip to content

[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes #245183

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+12 −2
Open

[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes #245183

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2f0aacb
First draft
nastasha-solomon Dec 4, 2025
24106a3
Updated ref
nastasha-solomon Dec 4, 2025
7afd5fd
Removed comment char
nastasha-solomon Dec 4, 2025
b44d2ec
Add period
nastasha-solomon Dec 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions docs/release-notes/breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,19 +39,29 @@ If you are migrating from a version prior to version 9.0, you must first upgrade
## 9.2.0 [kibana-9.2.0-breaking-changes]
$$$kibana-230067$$$
::::{dropdown} Improved advanced settings management APIs privilege checks
% **Details**<br> Roles with explicit `read` access to advanced settings but `all` access to `SavedObjectManagement` can no longer update settings using the internal advanced settings API. This update enforces explicit privileges instead of relying on saved object security checks.
**Details**<br> Roles with explicit `read` access to advanced settings but `all` access to `SavedObjectManagement` can no longer update settings using the internal advanced settings API. This update enforces explicit privileges instead of relying on saved object security checks.
View [#230067]({{kib-pull}}230067).
::::

## 9.1.0 [kibana-9.1.0-breaking-changes]
$$$kibana-213916$$$
::::{dropdown} Change to variable syntax in {{esql}} queries

% **Details**<br> Fields and functions variables are now described with `??` in {{esql}} queries. For value variables, you can continue to use `?`.
**Details**<br> Fields and functions variables are now described with `??` in {{esql}} queries. For value variables, you can continue to use `?`.

View [#213916]({{kib-pull}}213916).
::::

$$$kibana-216558$$$
::::{dropdown} API keys are used for authenticating report generation requests

**Details**<br> In 9.1.0, API keys are used for authenticating report generation requests, instead of session cookies that are based on user credentials.

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 local index, instead of the remote. For more information and examples, refer to [Configure roles and users for remote clusters](docs-content://deploy-manage/remote-clusters/remote-clusters-cert.md#remote-clusters-privileges-cert).

View [#216558]({{kib-pull}}216558).
::::

## 9.0.0 [kibana-900-breaking-changes]
$$$kibana-193792$$$
:::{dropdown} Access to {{kib}}'s internal APIs is blocked
Expand Down
Loading