mirror of
https://github.com/keycloak/keycloak.git
synced 2026-01-09 23:12:06 -03:30
1f9694358f
* Ability to enable/disable feature via single property Closes #43541 Signed-off-by: Martin Bartoš <mabartos@redhat.com> * Provide support for specifying profile preview Signed-off-by: Martin Bartoš <mabartos@redhat.com> * Remove duplication check, use the new WildcardOptionUtil Signed-off-by: Martin Bartoš <mabartos@redhat.com> * Create quarkus specific single profile config resolver Signed-off-by: Martin Bartoš <mabartos@redhat.com> * Remove the feature profile capability for single feature option Signed-off-by: Martin Bartoš <mabartos@redhat.com> --------- Signed-off-by: Martin Bartoš <mabartos@redhat.com>
41 lines
2.3 KiB
Plaintext
41 lines
2.3 KiB
Plaintext
// Release notes should contain only headline-worthy new features,
|
|
// assuming that people who migrate will read the upgrading guide anyway.
|
|
|
|
= Preview of enhanced HTTP performance
|
|
|
|
You can now enable a more efficient way to handle JSON data in the HTTP layer.
|
|
This change increases throughput by ~5%, stabilizes response times, and reduces system resource usage.
|
|
|
|
In order to apply it, you need to explicitly enable the feature `http-optimized-serializers`.
|
|
|
|
NOTE: This feature is *preview*.
|
|
ifeval::[{project_community}==true]
|
|
We gather more feedback about potential issues in https://github.com/keycloak/keycloak/discussions/43484[this discussion]. We appreciate any feedback.
|
|
endif::[]
|
|
|
|
For more details, see the https://www.keycloak.org/server/configuration-production[Configuring Keycloak for production] guide.
|
|
|
|
= Breaking Fix for Windows in Loopback Hostname Verification
|
|
|
|
This release introduces a breaking change for Windows users: setups that previously relied on custom machine names or non-standard hostnames for loopback (e.g., `127.0.0.1` resolving to a custom name) may require updates to their trusted domain configuration. Only `localhost` and `*.localhost` are now recognized for loopback verification.
|
|
|
|
Keycloak now consistently normalizes loopback addresses to `localhost` for domain verification across all platforms. This change ensures predictable behavior for trusted domain checks, regardless of the underlying OS.
|
|
|
|
= Export traces with custom request headers
|
|
|
|
It is now possible to set request headers for exporting traces via Open Telemetry Protocol (OTLP).
|
|
It is mainly useful for providing tokens in the request.
|
|
|
|
You can specify these headers via the `tracing-header-<header>` wildcard option, accepting any custom header name.
|
|
|
|
For more details, see the link:{tracingguide_link}[{tracingguide_name}] guide.
|
|
|
|
= Enable/disable features via a single option
|
|
|
|
You can now enable or disable individual features using the `feature-<name>` option (like `feature-spiffe=enabled`).
|
|
|
|
This provides a more fine-grained way to manage features and eliminates the need to maintain long lists of enabled or disabled features.
|
|
|
|
The `feature-<name>` option takes precedence over both `features` and `features-disabled`.
|
|
|
|
For more details, see the https://www.keycloak.org/server/features[Enabling and disabling features] guide. |