External-Mirrors/keycloak
2
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-01-10 15:32:05 -03:30
Code Issues Packages Projects Releases Wiki Activity

Rework formatting for release notes

Browse Source 
Closes #43320

Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
This commit is contained in:
Alexander Schwartz 2025-10-10 12:42:53 +02:00 committed by GitHub
parent c2e49c8c59
commit 934ac48a54
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 14 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
docs/documentation/upgrading/topics/changes/changes-26_4_0.adoc
View File

@ -12,19 +12,6 @@ This change enhances security by preventing unintended disclosure of authenticat
If you are relying on the `acr_values` parameter to be propagated to an identity provider, you must now explicitly set `acr_values` request parameter
to the `Forwarded query parameters` setting in the identity provider configuration.
=== Re-created indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables
In some previous versions of {project_name}, the EnterpriseDB (EDB) was considered unsupported. This has now changed and
EDB Advanced is supported starting with this release. If the EDB JDBC driver was used for connecting to EDB in previous versions,
some invalid schema changes were applied to the database. To mitigate this, some indexes are automatically re-created during
the schema migration to this version. **This affects you if you are using a Postgres database (including EDB), regardless if you
used EDB with previous releases.**
This affects indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables. If those tables contain more than 300000 entries,
{project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement
on the console during migration to be applied manually after {project_name}'s startup.
See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit.
=== Configuration changes for additional datasources
In previous releases, the only possible way to configure additional datasources was using raw Quarkus properties that are generally considered unsupported. At the same time, adding additional datasources was supported which led to unclear situation.
@ -110,7 +97,7 @@ If you are running {project_name} in FIPS 140-2 mode, note to update your Bouncy
With the upgrade to Bouncy Castle 2.1.x, EdDSA is now supported in FIPS 140-2 mode.
== Creating remote caches automatically on the first startup
=== Creating remote caches automatically on the first startup
When using remote caches, {project_name} now automatically creates the necessary caches during startup if they do not already exist on the {jdgserver_name} server.
@ -309,6 +296,19 @@ This implicit fallback mechanism ensures a smooth upgrade process for deployment
For more information about fine-grained admin permissions, see link:{adminguide_finegrained_link}[{adminguide_finegrained_name}].
=== Re-created indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables
In some previous versions of {project_name}, the EnterpriseDB (EDB) was considered unsupported. This has now changed and
EDB Advanced is supported starting with this release. If the EDB JDBC driver was used for connecting to EDB in previous versions,
some invalid schema changes were applied to the database. To mitigate this, some indexes are automatically re-created during
the schema migration to this version. **This affects you if you are using a Postgres database (including EDB), regardless if you
used EDB with previous releases.**
This affects indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables. If those tables contain more than 300000 entries,
{project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement
on the console during migration to be applied manually after {project_name}'s startup.
See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit.
=== Errors when searching users from LDAP will not fail the request anymore and local users will be returned
Until now, failures when searching for users from an LDAP user federation provider caused the whole request to fail and no users were returned.
@ -379,10 +379,3 @@ You should also review the other methods that are deprecated for removal in this
The `clientId` note in the authenticated client session is an internal note present only when using the embedded caches, and is now deprecated for removal. Instead, use the `getClient()` method.
// ------------------------ Removed features ------------------------ //
== Removed features
The following features have been removed from this release.
=== <TODO>