Re: FIPS Java API provider and non-FIPS provider
Matti Aarnio <[email protected]>
| Newsgroups | gmane.comp.encryption.bouncy-castle.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Tony, The detail that affects more than "in same JVM" is "are they in same class loader?" WARs are loaded into separate class loader chains. WAR1 gets loader chain: CL1, CLroot. WAR2 gets loader chain: CL2, CLroot. If neither BCFIPS nor BCPROV are in CLroot, and instead in separate WARs, then the libraries will not see each other, and no collision happens. The "CLroot" is server/lib/ in current Tomcats. The "CLn" is webapps/warname/WEB-INF/lib/ Best Regards, Matti On 05.06.2018 21:01, Rhuberg,Anthony wrote: > > We have an application deployed within Tomcat and that application is uses Apache CXF which has a dependency on bcprov-jdk15on-1.51. > > Referring to: https://www.bouncycastle.org/fips-java/BCFipsIn100.pdf: “The provider jar itself has no external dependencies, but it cannot be used in the same JVM as the regular Bouncy Castle provider. The classes in the two jar files do not get along”. > > We are integrating FIPS Java API provider into another application WAR. We have not encountered an issues yet, but wanted to know what kinds of errors are expected if two applications use different Bouncy Castle Java implementations within the same JVM. > > Thanks,Tony >