-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 17: JCE cannot authenticate the provider BC #26
Comments
i tried 2.0.0 with the dockerfile and didnt have any issues with the used java 17 |
See #27 for a fix. |
Maybe its the use of Java 17 also during the build in your commits? Upgrading to Java 17 in the build also would make sense though it should work with Java 11 for the build and running it with 17. |
@jakob-p wrote:
Maybe you are not using nested jar files there which seems to be the root cause. |
I'm currently working on updating the whole dockerfile / project to java 17 |
I pushed some changes to https://github.com/gtuk/diga-api-service/tree/update-java |
Using Java 17 and the new 2.0.0 release I seem to run into spring-projects/spring-boot#28837:
Local traceback for validation
According to spring-projects/spring-boot@33c5e12 this issue was fixed in 3.2.0rc1.
Do you think it is possible to try out the latest version (currently 3.2.0rc2) to get rid of this error? It currently prevents from using the new release and Java 17.
The text was updated successfully, but these errors were encountered: