[JENKINS-72249] switch to JcaContentSignerBuilder in order to obtain a ContentSigner #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JENKINS-72249 can not connect JNLP4 agents to controller with BC-FIPS configured
Switch implementation to use classes available in both regular and fips versions of bouncycastle.
AsymmetricKeyParameter
was available inbcprov
but not inbc-fips
.JCAContentSignerBuilder
is available in the regular bcpkix and bcpkix-fips.The higher level API also has the benefit that the code becomes more legible.
Testing done
tested a snapshot of this in a clean non fips environment and provisioned a k8s based agent using JNLP4.
tested a snapshot of this PR in the environment that exhibited the issue and validated that k8s based JNLP4 agents can launch without issue after this change.
Additionally excluded the bouncycastle jars and substituted in the bc-fips variants, registered the provider in the tests and ran the tests that covered this area (
mvn -Dtest=ReadWriteKeyTest InstanceIdentityTest
).expand to see the diff used
Submitter checklist