Using A Fully Qualified Domain Name That Differs From the Public-Facing Domain Name

07-24-2018 04:11 PM
Occasional Contributor

There's some great instructions for installing Portal in AWS and hooking it up such that the fully qualified domain name/Windows Domain/certificates/public access work.

Is there anything out there that describes what to do when the computer's fully qualified domain name is something like "test.InternalDomain.local" but the organization's public host name is something else like and the certificate is issued to "*"?

Assume that I am installing the latest version of Portal on the latest version of Windows Server.

0 Kudos
1 Reply
Esri Notable Contributor

Setting the Web Context URL should do the trick.

0 Kudos