Replies: 2 comments
-
Yes it is on the roadmap. Not until later however. WildFly 28 updates Jakarta EE to 10 This is a completely breaking change meaning that there will be a version of EJBCA that only runs on WF 28 and later, while the current version of EJBCA can only run on WF <=26. This is because Jakarta EE 10 completely removes any backwards compatibility, and an application can not be compatible with both. I hope this makes it understandable why this change can not be done just like that. It's actually the first time that Java EE completely breaks backwards compatibility (surprising to me). The CVE will have to be investigated/patched by you. To my knowledge none if them are remote-affecting, or EJBCA-affecting. You can use Galleon as described in the EJBCA install docs to remove unused modules. Cheers, |
Beta Was this translation helpful? Give feedback.
-
Thanks so much for your reply! |
Beta Was this translation helpful? Give feedback.
-
Hi!
The latest supported release of WildFly as per the documentation is
26.x
. Nevertheless, WildFly has yet released two new more versions, being the current one WildFly 28.Leaving new features aside, using a security scanner (like Trivy), we can see that the current version reports much fewer vulnerabilities:
WildFly 28
WildFly 26
Is supporting this new version in your roadmap so that users can benefit of up-to-date components? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions