AnsweredAssumed Answered

Server 10.1 -- HTTPS access using self-signed certificate without Web Adaptor install

Question asked by krdyke on Apr 6, 2013
Latest reply on Apr 8, 2013 by krdyke
Hi all,

I'm new to SSL certificates and all that, so I'm hoping someone could provide a little clarification.

First a little background. We have a simple ArcGIS Server site setup (let's call it, consisting of 1 machine. That one machine is named The application I've developed using the JavaScript API will ultimately be housed on a secured HTTPS location. In order to prevent browsers such as Chrome and IE from blocking content from my HTTP based server, I'm hoping to enable SSL on my server. None of the content being handled is sensitive or in need of security, really. It's simply that the ultimate location being HTTPS is breaking calls to the server.

When I look at the default selfsignedcertificate for, the common name on the certificate differs from the machine name, and is listed as

First question, if I simply were to enable SSL on the site (via while using the default self-signed cert, would the difference in the common name be enough to prevent it from working?

Second question, should the common name for the self-signed certificate match that of the site, or the server machine?

I'm just hoping to get a basic level of HTTPS support and from there move onto installing a CA signed certificate.

AGS is installed on Windows Server 2008 R2. Is there anything I need to do outside of AGS if I'm not using the Web Adaptor? Am I totally off-base with my thinking on this stuff (my feeling is that I probably am!).

I appreciate any advice or at least direction. I've followed the directions in the help to no avail, and have tried creating a self-signed cert with matching common names (I've tried to match the machine name in one instance and the site name in another).

Kevin ****