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
spring-boot-starter-remote-shell (1.2.5.RELEASE) needs org.bouncycastle:bcpkix-jdk15on (1.51), but having spring-security-jwt (1.0.3.RELEASE) as dependency leads to version 1.47 to be used.
This will cause errors when using the remote shell as the API of the bouncycastle library has changed considerably between 1.47 and 1.51. More precisely, it causes an exception when someone tries to connect to the remote shell: java.lang.IllegalStateException: Unable to negotiate key exchange for server host key algorithms.
However, the real issue is an InvocationTargetException which is thrown while trying to read the server key due to the incompatible API.
The text was updated successfully, but these errors were encountered:
stdll
changed the title
Dependency conflicht between spring-boot-starter-remote-shell and spring-security-jwt
Dependency conflict between spring-boot-starter-remote-shell and spring-security-jwt
Jul 15, 2015
When using both
spring-boot-starter-remote-shell
andspring-security-jwt
there is a version conflict concerningorg.bouncycastle:bcpkix-jdk15on
.Simple steps to replicate the issue:
spring-security-jwt
as dependencyThe POM should have the following dependencies:
spring-boot-starter-remote-shell
(1.2.5.RELEASE) needsorg.bouncycastle:bcpkix-jdk15on
(1.51), but havingspring-security-jwt
(1.0.3.RELEASE) as dependency leads to version 1.47 to be used.This will cause errors when using the remote shell as the API of the bouncycastle library has changed considerably between 1.47 and 1.51. More precisely, it causes an exception when someone tries to connect to the remote shell:
java.lang.IllegalStateException: Unable to negotiate key exchange for server host key algorithms
.However, the real issue is an
InvocationTargetException
which is thrown while trying to read the server key due to the incompatible API.The text was updated successfully, but these errors were encountered: