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
{{ message }}
Repository navigation
Keycloak 26.7 Compatibility with Oracle Database 26ai
#51722
Hi,
I'm checking if Keycloak v26.7 is compatible with Oracle 26ai. There are plans to migrate from 19c to 26ai, and we want to be sure that Keycloak is or will be compatible. The documentation (as of v26.7.1) lists Oracle Database 23.x (23.5+) and 19c (19.3+) as the tested/supported versions, but there's no mention of 26ai yet.
Environment:
Keycloak: 26.7.0, clustered (quarkus dist)
Target DB: Oracle 26ai, multitenant
JDBC: ojdbc17 / orai18n
Thanks!
Not supported, and it isn't a case of the docs lagging behind the code — the matrix on main (ahead of 26.7.1) still lists the same two.
That table has a single source, docs/guides/server/templates/databases.adoc, which the db.adoc and supported-configurations.adoc guides both render:
|Oracle Database <#if detailed>| `oracle` | ${properties["oracledb.version"]}</#if> | 23.x (i.e 23.5+), 19c (19.3+) (*Note:* Oracle RAC is also supported if using the same database engine version, e.g 23.5+, 19.3+)
So the absence of 26ai from the 26.7.1 docs reflects the current state of the support matrix rather than an unwritten entry.
The part that matters for a migration decision is the note directly under the table in docs/guides/server/db.adoc:
NOTE: It is not a supported configuration if the underlying database specific Hibernate dialect allows the use of a version that differs from those shown.
That is worth reading carefully in your position. Keycloak on 26ai may well start and run — the dialect will resolve, and ojdbc17 + orai18n are exactly the drivers Keycloak documents installing, so the driver layer isn't your obstacle. But "it works in our test cluster" and "supported" are explicitly different things here, and this note exists to close that gap in advance. If support status is a requirement for the migration rather than a nice-to-have, 26ai does not currently satisfy it at any Keycloak version.
I also searched issues for Oracle 26ai and found nothing open or closed, so there's no tracking item to subscribe to and no signalled timeline. If you're planning the 19c → 26ai move on a real schedule, opening one is worth doing — a concrete deployment description (26.7.0, clustered Quarkus dist, multitenant, ojdbc17/orai18n) is more actionable for whoever owns the matrix than a generic "will you support X" request, and it gives you something to watch. Right now the answer to "is it or will it be compatible" has no public position either way.
One detail specific to your setup: multitenant/CDB is worth calling out explicitly in that request. The supported-versions column speaks to engine versions, and the RAC note is the only deployment-topology carve-out in it — so a multitenant deployment on a new major is two variables away from what is currently tested, not one.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I'm checking if Keycloak v26.7 is compatible with Oracle 26ai. There are plans to migrate from 19c to 26ai, and we want to be sure that Keycloak is or will be compatible. The documentation (as of v26.7.1) lists Oracle Database 23.x (23.5+) and 19c (19.3+) as the tested/supported versions, but there's no mention of 26ai yet.
Environment:
Keycloak: 26.7.0, clustered (quarkus dist)
Target DB: Oracle 26ai, multitenant
JDBC: ojdbc17 / orai18n
Thanks!
All reactions
Replies: 1 comment
Uh oh!
There was an error while loading. Please reload this page.
Not supported, and it isn't a case of the docs lagging behind the code — the matrix on
main(ahead of 26.7.1) still lists the same two.That table has a single source,
docs/guides/server/templates/databases.adoc, which thedb.adocandsupported-configurations.adocguides both render:So the absence of 26ai from the 26.7.1 docs reflects the current state of the support matrix rather than an unwritten entry.
The part that matters for a migration decision is the note directly under the table in
docs/guides/server/db.adoc:That is worth reading carefully in your position. Keycloak on 26ai may well start and run — the dialect will resolve, and
ojdbc17+orai18nare exactly the drivers Keycloak documents installing, so the driver layer isn't your obstacle. But "it works in our test cluster" and "supported" are explicitly different things here, and this note exists to close that gap in advance. If support status is a requirement for the migration rather than a nice-to-have, 26ai does not currently satisfy it at any Keycloak version.I also searched issues for Oracle 26ai and found nothing open or closed, so there's no tracking item to subscribe to and no signalled timeline. If you're planning the 19c → 26ai move on a real schedule, opening one is worth doing — a concrete deployment description (26.7.0, clustered Quarkus dist, multitenant,
ojdbc17/orai18n) is more actionable for whoever owns the matrix than a generic "will you support X" request, and it gives you something to watch. Right now the answer to "is it or will it be compatible" has no public position either way.One detail specific to your setup: multitenant/CDB is worth calling out explicitly in that request. The supported-versions column speaks to engine versions, and the RAC note is the only deployment-topology carve-out in it — so a multitenant deployment on a new major is two variables away from what is currently tested, not one.
All reactions