springboot wolfjsse fixes

[JeremiahM37]

wolfJSSE Compatibility Improvements for Spring Boot

Summary

These changes improve wolfJSSE compatibility with Spring Boot's SSL/TLS testing infrastructure, enabling 266 Spring Boot tests to pass. The updates align behavior with standard SunJSSE expectations, specifically regarding exception types and session state management.

---

Changes

WolfSSLEngine.java

• Throw SSLHandshakeException during handshake errors: Changed to throw SSLHandshakeException instead of a generic SSLException when errors occur before handshake completion. Spring Boot tests check exception types to distinguish handshake failures from other SSL errors.

WolfSSLEngineHelper.java

• Track client auth state: Pass clientAuthRequested flag to session when needClientAuth or wantClientAuth is set, enabling proper getPeerCertificates() behavior.

WolfSSLImplementSSLSession.java

• Fix getPeerCertificates() behavior: Throw SSLPeerUnverifiedException when called on server-side with no client auth requested (instead of returning null). This matches SunJSSE behavior that Spring Boot expects.
• Fix getPeerCertificateChain() behavior: Throw exception instead of returning null when no peer certificate is available.

WolfSSLKeyX509.java

• Fix chooseClientAlias() / chooseEngineClientAlias(): Skip certificate-only entries (trustedCertEntry) that have no private key. Previously, this would return aliases for trust anchors that could not be used for client authentication.

WolfSSLTrustManager.java

• Support CertPathTrustManagerParameters: Implement engineInit(ManagerFactoryParameters) to handle CertPathTrustManagerParameters, extracting trust anchors and creating a KeyStore. Used by Tomcat and Spring Boot for SSL configuration.
• Support KeyStoreBuilderParameters: Also handle KeyStoreBuilderParameters for applications that use KeyStore builders.

WolfSSLUtil.java

• Null-safe sanitizeProtocols(): Return null early if protocols array is null, preventing NullPointerException.