Do you use Bouncy Castle and want to migrate to wolfSSL’s Java providers – wolfJSSE and wolfJCE? If so, we just published a Bouncy Castle Migration Guide!
wolfJSSE and wolfJCE are Java Security Providers that sit on top of native wolfCrypt and wolfSSL for cryptography and SSL/TLS functionality. Common advantages to using wolfSSL include progressive algorithms (including Post Quantum crypto), assembly or hardware-based cryptography acceleration, FIPS 140-3 validated cryptography, commercial support, and portability.
Our Bouncy Castle Migration Guide includes sections for:
- JCE Provider Migration
- JSSE Provider Migration
- Bouncy Castle Proprietary API Migration
- FIPS 140-3 Considerations
- Troubleshooting
JCE and JSSE migration is very straightforward, and commonly only requires changing the provider registration or usage of a different provider name programmatically. Bouncy Castle proprietary API migration can be done on a use case basis. Our guide walks you through some of the common use cases, including X.509 certificate extensions, X.509 certificate generation, X.509 certificate verification, CRL generation, RSA encryption/signing/verifying, hex string encoding, PEM to DER conversions, and more. If we left something out, send us a note to support@wolfssl.com and we will try to fill in the gaps!
This new guide is a supplement to the wolfSSL JNI/JSSE User Manual and wolfCrypt JNI/JCE User Manual.
If you have FIPS 140-3 requirements, we regularly add Operational Environments to our existing certificates, and can do so quickly and easily.
If you have questions about using wolfSSL, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now