The current SslX509Provider relies on an overly complex, legacy Netty port (JdkSslServerContext -> JdkSslContext -> SslContext) just to parse PEM files and instantiate a standard Java SSLContext. Most of this hierarchy consists of dead code or redundant cipher configurations.
We need to simplify this to match the clean, native-Java approach used in SslPkcs12Provider.
The current SslX509Provider relies on an overly complex, legacy Netty port (JdkSslServerContext -> JdkSslContext -> SslContext) just to parse PEM files and instantiate a standard Java SSLContext. Most of this hierarchy consists of dead code or redundant cipher configurations.
We need to simplify this to match the clean, native-Java approach used in SslPkcs12Provider.