All,
I have successfully installed and configured ArcGIS 10.6 (single site deployment) ArcGIS server federated with Portal. This is almost brandnew portal. Now business team wants change in application url.i.e. DNS alias needs to be changed.
Portal url: https://gisportal.domain.com/portal/home - now business asks me to change to https://gishub.domain.com/portal/home. I would like to know the basic high level steps for this change.
I got a new signed SSL certificate for gishub.domain.com and updated new DNS alais to machine name. Do I just need to reconfigure web adaptor with new dns alais or any
other steps involved,.
You can lock down your web server so that only client requests to your portal go through the DNS alias. Your backend config can then continue with hostname, e.g. web adaptor config, federation url's. In my opinion, you should not need to change anything besides stopping access via the hostname url. I have built Enterprise GIS' and had IT provide a DNS alias for all machines weeks after the fact with no issues / requirements to change any config on my end.
Good to know. So during installation you simply used the hostnames where required e.g. URL's for federating ArcGIS Server with Portal? Once you had the DNS alias' created you didnt alter any config like WebContextURL?
I was prepared to edit the WebContextURL, but did not do so by default. I attributed this to the hardiness of the esri stack and/or fluke.
All URL's were FQDN during the install & configuration. The only change in this space is that the Portal Web Adaptor URL was configured to the DNS after installation & configuration. In portaladmin/system/webadaptors/<ID>/edit
we have https://DNS_Alias/arcgis, instead of https://FQDN/arcgis.
Standard user behaviour when navigating the 2D map viewer contains DNS alias references to my Portal & DNS alias references to my basemap server. Not a FQDN or broken GET request in sight.
Thanks for the information Angus Hooper !
I don't know how you found this though ! I could not find anything in the documentation regarding this REST "/edit" endpoint and it does not show up on the HTML portaladmin interface:
https://developers.arcgis.com/rest/enterprise-administration/portal/web-adaptor.htm
It was really useful for me as Portal for ArcGIS automatically configured FQDN webadaptor URL for SAML Service provider urls config.
I'm surprised you didn't need to update the WebContextURL as Finnian O'Connor mentioned. Portal will want to redirect to the internal machine name or privatePortalURL if the incoming request isn't from the WebContextURL.
I've spent a couple of hours reading about reinstalling webAdaptors och refederating ArcGIS Server wich I thought I might have to do to change our portal urls from machine.domain.com to a new DNS name. But are you saying it's as easy as just an edit in the portaladmin interface? certainly not easy to find but easy to do once you found it. Should I just edit the "Web adaptor URL" with my new DNS-name? as the example in the attached screenshot?
That looks correct. Keep in mind that the rollback is quite easy, just change it back to machine name.
Also, this only applies for Portal for ArcGIS. ArcGIS Server does not allow you to /edit the web adaptor endpoint. In order to achieve the same end result you'll need to reinstall the WA and ensure you access the configuration endpoint via the DNS alias from the local machine when configuring it. This may not be relevant for the recent releases though as the web adaptor config process has been tweaked by the looks of it.
Hey,
I have successfully installed and configured ArcGIS 11.0 .ArcGIS server federated with Portal. This is almost brandnew portal. Now business team wants change in application url. DNS alias needs to be changed.
Portal url: https://cbs/portal/home - now business asks me to change to https://cbs.kentinrehberi.com/portal/home. I would like to know the basic high level steps for this change.
cbs: computer name
sslname:kentinrehberi.com
I got a new signed SSL certificate for *.kentinrehberi.com.
what should I do?
If it is almost a brand new site then I would contemplate rebuilding it with that DNS alias in mind.
Also, I would encourage you not to use the computer name in the URL or alias. Future proof yourself and make sure every component has a friendly alias, i.e. portal.companyname.com, maps.companyname.com.