mirror/keycloak
1
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-05-04 22:21:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] Additional datasources support (#42655)

Browse Source 
* [Docs] Additional datasources support

Closes #40388

Closes #42263

Co-authored-by: Václav Muzikář <vaclav@muzikari.cz>
Signed-off-by: Martin Bartoš <mabartos@redhat.com>

* Rename namedKey to wildcardKey in the code

Signed-off-by: Martin Bartoš <mabartos@redhat.com>

* Clarify the defaults for DB kind

Signed-off-by: Martin Bartoš <mabartos@redhat.com>

* Be more clear about the Named key reference in guide

Signed-off-by: Martin Bartoš <mabartos@redhat.com>

* Vasek's review

Signed-off-by: Martin Bartoš <mabartos@redhat.com>

---------

Signed-off-by: Martin Bartoš <mabartos@redhat.com>
Co-authored-by: Václav Muzikář <vaclav@muzikari.cz>
This commit is contained in:
Martin Bartoš
2025-09-27 10:45:12 +02:00
committed by GitHub
parent 6e851ce80e
commit f53e5ebdac
32 changed files with 848 additions and 660 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/documentation/release_notes/topics/26_4_0.adoc
+9
View File
@@ -175,3 +175,12 @@ When this option is set, Infinispan will automatically replicate the cache data
With this release, we added support for the following new database vendors:
* EnterpriseDB (EDB) Advanced 17.6
= Additional datasources configuration is supported
Some {project_name} use cases (like User Federation) might require connecting to additional databases.
This was possible only through specifying unsupported raw Quarkus properties in previous {project_name} versions. In this release, we've refined dedicated server options for additional datasources and promoted them to supported. This allows users to leverage additional databases in their extensions in a supported and user-friendly way.
Read more about it in the link:https://www.keycloak.org/server/db#configure-multiple-datasources[Configure multiple datasources] guide.
For the information about the necessary migration from the old configuration to the new one, see the link:{upgradingguide_link}[{upgradingguide_name}].