I am trying to get Portal 10.3.1 installed and work with my instance of ArcServer 10.3.1
I am working on a domain on a strictly internal LAN created by our SA and named with a .local suffix. I am just now learning about how .local domains are problematic now. http://www.mirazon.com/so-you-have-a-local-domain-now-what/ My SA launched a local Certificate authority for me, created a certificate named server.dommainname.local, and I thought I got it working on the local IIS and bound it to port 443. However, client connections from browsers still report security problems. The cert is not recognized.
ESRI tech support ran through the set up with me with screen share, then elevated me to next tier tech support, and they finally blamed the cert my SA generated.
I talked to GoDaddy about buying a cert from them, but they told me their certs will not work on a .local domain. They said domains like this are not longer “fully functional domain names”, starting in Nov. 2015. But will this also not work if we generate a domain cert from our local authority? Is this because the local domain is named *.local?
Shooting from the hip here, since I did not create our self-signed cert, and we are working with ArcGIS Server, non-federated....however, we were having issues with our proxy and secured services on our strictly in-house machine. Came down to the self signed cert. My IT guy said something about it not liking the .domain.local part of the cert.
Out IIS is setup to be https://gisdev105 without needing the .domain.local when we can the web pages. The original cert I think included the .domain.local From what I understand, he creted a new self-signed cert to match the gisdev105 portion only. So our proxy now works with our secure/non-secure services (just not totally with our custom print service...but that is another thread).