Adding certificates to the SSLContext of the BouncyCastleJsseProvider/ProvSSLContextSpi

[jubui]

I have a custom SSLContext.TLS provider and extend SSLContextSpi by adding extra certs to our TrustManager. This provider is at the highest priority and takes precedence over our SunJSSE provider. I am wondering if adding BouncyCastleJsseProvider / ProvSSLContextSpi will conflict with our custom provider because the one provided by ProvSSLContextSpi will not have those extra certificates and it doesn't seem like there's a way to inject them. In other words, it seems anyone who wants bcfips and its TLS implementation, will lose control over how the SSLContext is initialized - specifically they cannot control the TrustManager and KeyStoreManager that are passed to the SSLContext. Is there a way to get around this limitation?