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: docs/documentation/upgrading/topics/changes/changes-26_4_0.adoc
+14-21Lines changed: 14 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,6 @@ This change enhances security by preventing unintended disclosure of authenticat
12
12
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
13
13
to the `Forwarded query parameters` setting in the identity provider configuration.
14
14
15
-
=== Re-created indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables
16
-
17
-
In some previous versions of {project_name}, the EnterpriseDB (EDB) was considered unsupported. This has now changed and
18
-
EDB Advanced is supported starting with this release. If the EDB JDBC driver was used for connecting to EDB in previous versions,
19
-
some invalid schema changes were applied to the database. To mitigate this, some indexes are automatically re-created during
20
-
the schema migration to this version. **This affects you if you are using a Postgres database (including EDB), regardless if you
21
-
used EDB with previous releases.**
22
-
23
-
This affects indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables. If those tables contain more than 300000 entries,
24
-
{project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement
25
-
on the console during migration to be applied manually after {project_name}'s startup.
26
-
See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit.
27
-
28
15
=== Configuration changes for additional datasources
29
16
30
17
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
110
97
111
98
With the upgrade to Bouncy Castle 2.1.x, EdDSA is now supported in FIPS 140-2 mode.
112
99
113
-
== Creating remote caches automatically on the first startup
100
+
=== Creating remote caches automatically on the first startup
114
101
115
102
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.
116
103
@@ -309,6 +296,19 @@ This implicit fallback mechanism ensures a smooth upgrade process for deployment
309
296
310
297
For more information about fine-grained admin permissions, see link:{adminguide_finegrained_link}[{adminguide_finegrained_name}].
311
298
299
+
=== Re-created indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables
300
+
301
+
In some previous versions of {project_name}, the EnterpriseDB (EDB) was considered unsupported. This has now changed and
302
+
EDB Advanced is supported starting with this release. If the EDB JDBC driver was used for connecting to EDB in previous versions,
303
+
some invalid schema changes were applied to the database. To mitigate this, some indexes are automatically re-created during
304
+
the schema migration to this version. **This affects you if you are using a Postgres database (including EDB), regardless if you
305
+
used EDB with previous releases.**
306
+
307
+
This affects indexes on the `CLIENT_ATTRIBUTES` and `GROUP_ATTRIBUTE` tables. If those tables contain more than 300000 entries,
308
+
{project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement
309
+
on the console during migration to be applied manually after {project_name}'s startup.
310
+
See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit.
311
+
312
312
=== Errors when searching users from LDAP will not fail the request anymore and local users will be returned
313
313
314
314
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
379
379
380
380
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.
381
381
382
-
// ------------------------ Removed features ------------------------ //
383
-
== Removed features
384
-
385
-
The following features have been removed from this release.
0 commit comments