BI Publisher MS clients unable to connect https; https web clients work flawlessly

1844981

Our security team required our internal publishing server be moved onto https ports

Our server has a self-signed certificate

All major web browsers can get to BI publisher UR:L https://example.com:9503/xmlpserver and login OK (after accepting the self signed certs)

All major web browsers can get to BI publisher UR:L http://example.com:9502/xmlpserver and login OK

Im testing FF 63.08b,  Chrome 70, Edge 38.14393.2068.0

The MS client get this at login for https

"The request was aborted: Could not create SSL/TLS secure channel."

The http insecure path  works on the exact same windows client.

Any debugging assistance as I'm not a Win10 expert?

Clients are

Win 10 1607

Office 2016

BiPublisherDesktop64.exe

Server:

OBIEE 12c on Linux

Is it because of Windows/Office doesn't trust my server's certificate?

I don't want to spend money on an internal only resource getting an external TLS validated cert just to test this theory.

Thank you!

Gianni Ceresa

Google seems to often point to "TLS 1.1 and TLS 1.2" related to that error. Apparently by default those protocols aren't always supported and need to be enabled in the registry or newer versions of .net runtime etc.

If that's the case it isn't because you have a self-signed certificate.

Could you ask your security guys if they are aware of this topics and can look into it (after all it's their fault that you are moving to HTTPS ).

User_6JJLV

https://community.oracle.com/tech/apps-infra/discussion/4180992/bi-publisher-ms-clients-unable-to-connect-https-https-web-clients-work-flawlessly

Did you ever get a fix for this as we are also having the same issue, latest win 10, latest .net, latest BI installer, so not sure why the BI app still trying to use TLS v1