Can one Enterprise Instance Support Multiple Domain Names?

[PeterKnoop]

Our goal is to host ArcGIS StoryMaps on ArcGIS Enterprise on a variety of domain names, rather than being stuck using storymaps.arcgis.com via ArcGIS Online. We could setup an Enterprise instance for each domain name, however, I am wondering if there is a way to configure one ArcGIS Enterprise instance to serve multiple domain names, so that it could serve StoryMaps on different domains?

[berniejconnors]

That sounds like a networking issue. Couldn't you setup rules on your proxy server to redirect multiple domains to a single ArcGIS Enterprise install? I rely on our network team for stuff like this so I can't provide more detail.

Bernie.

GeoNB.

[berniejconnors]

Peter,

         We publish many map viewers with the AGOL hosted WAB. We take the AGOL URL for the WAB app and iframe it into a bare bones html page that is hosted under our domain name geonb.snb.ca.  This allows us to include our Google Analytics code with the WAB app.  Have a look at the html source for this page for an example - https://geonb.snb.ca/geonb/index.html.  This should work for story maps too.

Bernie.

GeoNB

[Scott_Tansley · Accepted solution]

Good question.  Unfortunately the answer is no.  

the rewrites that happen without the application rely on a  single url.  

When you create the first ‘item’ you lock in the subdomain.  Changing the url after this point is unsupported.

you could use workarounds though.  A seperate web server could be used to act as the url you want.  A simple HTML page could have an iframe or a redirect that points to a specific app.  Redirects can also be crated with IIS rules or similar.  This is a valid approach but the underlying web traffic must always point to a single ArcGIS Enterprise subdomain. 

sorry, that may not be the answer your want, but it is the case. 

[DEWright_CA]

A Option that is available is a seperate Portal Instance with a Collaboration configured. Through the proper use of groups and permissions you can proxy to another URL quite well.

[PeterKnoop]

Thanks, @Scott_Tansley. I was afraid that would be the case.

@berniejconnors and @Scott_Tansley, the suggested iframe workaround does work for some use cases with StoryMaps, however, we were hoping for a universal solution. The iframe approach on its own fails for a subset of StoryMap functionality, such as when using links to sections within a StoryMap, where you don't have control over the URL. Will take a look to see if redirects or proxies can help us out with that use case.

[HarryPlend1]

Situation:

Our Portal can be reached by the outside domain but the custom web application published and registered with Portal cannot. Other built in experience builder sites and dashboards can be accessed from outside domains, but not our custom web application.

Observation:

What I read in this solution is that the web application has a single URL which can't be changed to support different domain names.

Details of the Situation:

The internal domain (pretend domain name) "https://small.pretty.ducks.org" is hard coded into the config file of the application, was the domain for publishing all the consumed services, and is also the same domain name used to configure the web adaptor.

There is the external domain (pretend domain name) "https://small.mallards.org" which is supposed to be the way people outside the organization are accessing the application. I believe the intent was to resolve the URL with subject alternative names in the SSL certificate. 

What is happening is people can get to the Portal home page ( https://small.mallards.org/Portal ) and other COTS apps but the custom app is inaccessible (https://small.mallards.org/CoolApp ). Internally, everyone and everything works fine. 

Context of Question:

What discovered in trouble shooting this problem was that there was nothing configured for the domain controller in the portal admin site. Configure the domain controller—Portal for ArcGIS | Documentation for ArcGIS Enterprise

{

"type": "WINDOWS",

"properties":

{ "userPassword": "secret",

 "isPasswordEncrypted": "false",

 "user": "mydomain\\winaccount",

 "userFullnameAttribute": "cn",

 "userEmailAttribute": "mail",

 "caseSensitive": "false",

 "domainControllerAddress": "[IP Address], [alternate IP Address]",

 "domainControllerMapping": "domain_A.example.com=[IP address], [alternate IP address]; domain_B.example.com=[IP address], [alternate IP address]"

}

}

Question: Would adding the domain controller mapping, alternative domain controller and IP address possibly, resolve the application internal URL/single URL issue? 

[ScottTansley3]

This sounds more like an infrastructure thing than a configuration thing. Let's say that you have a 'portal' with all its apps and it sits on a machine called mylittle.yellowrubberducky.com, the chances are that the machine is within a secure network and no one from outside can communicate with it.

The way we deal with this is to have a secure perimeter zone and we put a web server in it with web adaptors. This machine may be called donald.duck.com. Outside in the big bad internet we create a DNS entry called vampireducks.rock.com and we create some IT magic rules that sends web requests directed at "vampire" to "donald" (via firewall), which in turn 'proxies' them to mylittle.yellow.

We have a chain of events.  If you deploy your custom app on donald, then it will be accessible via making requests to your vampire duck, but if you've deployed it on mylittle.yellow then the big bad outside can't communicate with  your app because it's protected by firewalls and other things that our IT departments like to use purely so they can give us a bad day...