Repository navigation
Replies: 3 comments 1 reply
|
WildFly has recently introduced native support with OIDC, Spring Security has done the same. That effectively means it makes no sense for us to continue the effort with WildFly and Spring adapters. Tomcat and Jetty adapters do have some use, but it is quite limited, and we can't really justify the effort required to keep them alive for a very small user base. In terms of modernising the adapters, there is also a fairly big gap between what we support today on the adaptor side and what we support on the server side around OIDC and OAuth. |
|
any chance to have a keycloak adapter for jetty 10 ? |
|
Afraid not, we're phasing out all adapters and won't update them to support new versions. |
|
Rejecting this as we are phasing out all adapters, see https://www.keycloak.org/2022/02/adapter-deprecation.html for more details. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello!
I'd like to discuss here some aspects related to Keycloak Java adapters, because I think, it'd be great to improve them. At this moment, in our codebase, we support particular Java adapters for Tomcat, Jetty and so on. However, the supported versions are quite old and it'd be good to upgrade them and support more modern application servers.
For instance, we provide adapters for Jetty 9.2, 9.3 and 9.4, but Jetty 10.x and even Jetty 11.x is released at this moment. IMO, it'd worth it to get rid of the 9.2 and 9.3 (deprecated) Jetty adapters and rather support more recent versions. Of course, it's necessary to find out, if it's really worth the effort and if the community would be glad to have it. At least, from QE perspective, it'd be great to test the newest application servers, because we don't know if our current adapters really works with them (assume not).
The same issue is similar for the Apache Tomcat, where we provide 7, 8 and 9 version. However, Tomcat 7 is deprecated and it'd be good to consider if we have some needs to support it. There's also a new Tomcat 10 release and we don't know if our current Tomcat adapter works with it. There's also extended version of the Apache Tomcat application server with name TomEE. However, everything depends largely on customer requests and needs, right?
I'd like to find out the current status of Keycloak adapters and their planned future. IMO, it'd be great to keep them alive and bring them up to date with the times.
WDYT? cc: @stianst, @hmlnarik, @mhajas, @pdrozd, @miquelsi
All reactions