Apr 26, 2006 05:00 PM|jjstreic|LINK
RPC/HTTPS requires HTTPS to function. The key is that the certificate matches exactly the name of the server used in the profile configuration. i.e. the cert must be valid for server.foo.com if server.foo.com is what your clients will access.
As long as all the clients trust the Certificate Authority it will work. For a hoster, this most likely means they have procured a commercial cert from someplace like Verisign or any other public CA.
Does that make sense?