keycloak/docs/documentation/release_notes/topics/26_6_0.adoc
Václav Muzikář d45dfeb44a
Java 25 support (#45872)
Closes #45905

Signed-off-by: Václav Muzikář <vmuzikar@ibm.com>
2026-02-10 23:35:35 +00:00

37 lines
1.8 KiB
Text

// Release notes should contain only headline-worthy new features,
// assuming that people who migrate will read the upgrading guide anyway.
= Sensitive Keycloak information is not displayed in the HTTP Access log
If you are using the HTTP Access logging capability, sensitive information is omitted.
It means that tokens in the 'Authorization' HTTP header and specific sensitive Keycloak cookies are not shown.
For more information, see https://www.keycloak.org/server/logging#http-access-logging[Configuring HTTP access logging].
= HTTP access logs in a dedicated file
HTTP access logs can now be written to a dedicated file, separate from the server logs.
This makes it easier to process and archive access logs independently for security auditing and compliance monitoring.
For more information, see https://www.keycloak.org/server/logging#http-access-logging[Configuring HTTP access logging].
= Telemetry configuration via Keycloak CR
{project_name} now supports configuring the OpenTelemetry properties via Keycloak CR when using Operator.
These properties are shared among the available OpenTelemetry components - logs, metrics, and traces.
For more details, see the link:{telemetryguide_link}[{telemetryguide_name}] guide.
= Custom request headers for OpenTelemetry
It is now possible to set request headers for exporting telemetry via OpenTelemetry Protocol (OTLP).
It is mainly useful for providing tokens in the request.
You can specify these headers via the general parent option `telemetry-header-<header>` wildcard option, accepting any custom header name.
Or you can use the `telemetry-logs-header-<header>` for OpenTelemetry Logs, or `telemetry-metrics-header-<header>` for OpenTelemetry Metrics.
For more details, see the link:{telemetryguide_link}[{telemetryguide_name}] guide.
= Java 25 support
{project_name} now supports running with JRE 25.