-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
JVM with BouncyCastle-FIPS installed.
-
-
instance-identity:185.v303dc7c645f9
when the JVM is configured to use bouncycastle-fips the agents can not connect to JNLP-4 based remoting due to an incompatibility between the classes in the fips and non fips variety of bouncycastle.
Oct 24, 2023 2:03:26 PM INFO jenkins.model.identity.InstanceIdentityProvider$KeyTypes getCertificate Encountered an error while consulting instance identity provider org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider@5b8b62a0 java.lang.ClassNotFoundException: org.bouncycastle.crypto.params.AsymmetricKeyParameter at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:476) at jenkins.util.URLClassLoader2.findClass(URLClassLoader2.java:35) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:594) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:527) Caused: java.lang.NoClassDefFoundError: org/bouncycastle/crypto/params/AsymmetricKeyParameter at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.getCertificate(InstanceIdentity.java:163) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getCertificate(InstanceIdentityRSAProvider.java:48) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getCertificate(InstanceIdentityProvider.java:299) at jenkins.slaves.JnlpSlaveAgentProtocol4.init(JnlpSlaveAgentProtocol4.java:86) at jenkins.slaves.JnlpSlaveAgentProtocol4.handle(JnlpSlaveAgentProtocol4.java:158) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:276)
- links to