The endpoint is a Secure Sockets Layer (SSL) connection, which will have a certificate in place. The Remote Connectivity Analyzer displays a warning if the certificate that is used for SSL cannot be trusted up to the root.
This issue typically occurs when the Web server certificate on the Client Access server is a self-signed certificate or one that was created by using a private or internal PKI.
This issue can also occur if certificates are chained to a CAS by another intermediate certificate.
The Remote Connectivity Analyzer queries the Authentication Platform in the cloud to perform a realm discovery.
When that process is finished, Authentication Platform passes to the requesting client the ADFS endpoint URL that the client requires for authentication.
This used to work before, but maybe the server has been changed.
However, if the certificate is not trusted subversion will ask you whether you trust the certificate and if you want to add this certifacte.
In order for the Remote Connectivity Analyzer to validate a given X509 certificate, the toll must trust the root Certificate Authority (CA) that issued the certificate.
If the tool cannot follow the certificate chain to the trusted root, it displays an error indicating that the certificate is not trusted.
This can occur if the if the RADIUS certificate, or any certificate in the chain, is configured or CRL or OCSP.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site.
However, the Outlook Anywhere (RPC over HTTP) connectivity tests currently require a publicly-trusted certificate that is also trusted by the server.