[Bug]: BC-FIPS compliant app breaks on Beam 2.39.0 when upgrading from 2.34.0
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What happened?
We're currently using a GCP Dataflow app which works fine under 2.34.0, but needs to remain FIPS compliant, this includes having bc-fips-1.0.2.1.jar in our classpath. When we tried to upgrade to 2.39.0, apparently this new version included the jar bcpkix-jdk15on:1.67, which collides with the FIPS implementation, according to this StackOverflow answer: [https://stackoverflow.com/a/71075642](https://stackoverflow.com/a/71075642)
The actual error is as follows:
`org.apache.beam.sdk.util.UserCodeException: java.lang.NoSuchMethodError: 'boolean org.bouncycastle.crypto.CryptoServicesRegistrar.isInApprovedOnlyMode()' at
org.apache.beam.sdk.util.UserCodeException.wrap(UserCodeException.java:39)`
Is there a way we can upgrade safely?
### Issue Priority
Priority: 2
### Issue Component
Component: io-java-gcp
Contributor guide
Assessment
This issue has not been assessed yet.