topic Re: CORS error with ExB Developer Edition and Enterprise in ArcGIS Experience Builder Questions

CORS error with ExB Developer Edition and Enterprise

MarcBate — Mon, 16 May 2022 20:21:05 GMT

When accessing ExB Developer edition via https://localhost:3001, and entering our ArcGIS Enterprise 10.9.1 address on the page https://localhost:3001/page/set-portalurl , it says "Your application domain is not allowed via Cross-Origin Resource Sharing (CORS) to access" then url of our portal web adaptor.

I tried to allow localhost in the Organization > Settings > Security page in the Portal, but it won't let me add it or https://localhost:3001

How do we use ExB Dev with our Enterprise server? I can only get it to work with AGOL.

Re: CORS error with ExB Developer Edition and Enterprise

GuillaumeArnaud — Mon, 16 May 2022 21:22:41 GMT

Hi ! If you have frontal of webadaptator of portal on IIS, verify if param accept CORS. Look your web.config file. An example can be find here : https://docs.microsoft.com/en-us/iis/extensions/cors-module/cors-module-configuration-reference . The same thing is available for Apache.

Guillaume

Re: CORS error with ExB Developer Edition and Enterprise

AzinSharaf — Tue, 17 May 2022 15:54:13 GMT

I am using my machine's fqdn (https://my_machine_fqdn:3001 and added this url to Portal security page. You may need use a CORS browser extension (link) as well to disable it.

Re: CORS error with ExB Developer Edition and Enterprise

MarcBate — Wed, 18 May 2022 16:15:39 GMT

This does not work and is most likely not recommended. There is another post marked as the solution, i.e. use the FQDN instead of localhost when accessing the ExB Dev edition and add that to the list of Allowed Origins in Portal Organization Security settings page

Re: CORS error with ExB Developer Edition and Enterprise

AzinSharaf — Wed, 18 May 2022 17:01:18 GMT

Editing web.config to allowing CORS is a Microsoft solution (the link Guillaume mentioned) and I can't say is not recommended unless you use "localhost" in web.config.

I think using "allow origin" does the same thing in Portal. But regardless, you cannot use localhost on either of the solutions for security reason,

Re: CORS error with ExB Developer Edition and Enterprise

DougSims_GT — Mon, 30 Jan 2023 16:24:31 GMT

"I can only get it to work with AGOL."

I'm still getting this error even using AGOL.

Even after adding my machine's FQDN to the allow list, I still get the CORS error when trying to register the app on my desktop.

Am I missing something obvious here?

Re: CORS error with ExB Developer Edition and Enterprise

ADM48 — Wed, 01 Feb 2023 23:55:43 GMT

Yup same here. My application is in AGOL and I've added the domain to the allow list.

Re: CORS error with ExB Developer Edition and Enterprise

DougSims_GT — Thu, 02 Feb 2023 15:09:10 GMT

The first problem I had was that I entered my server and my desktop into the list of "Trusted Servers" instead of the "Allowed origins" section.

I had originally added our top level domains to the allowed origins list, thinking that would cover all of our servers, but I discovered that domain wildcards are not allowed in that list. (Which seems like an odd limitation.)

Adding my server name and my desktop FQDN to the allowed origins list fixed the issue for me.

Re: CORS error with ExB Developer Edition and Enterprise

boro — Tue, 13 Feb 2024 15:28:58 GMT

Can you explain how you did this? If i try to add my FQDN to the list of Allowed Origins it starts complaining baout missing a domain name...

Re: CORS error with ExB Developer Edition and Enterprise

DougSims_GT — Tue, 13 Feb 2024 15:40:35 GMT

If there is no domain in your entry, then it isn't a Fully Qualified Domain Name. You will need a full domain name for it to register correctly.

Are you trying to do this on your desktop/laptop or on a server?

Re: CORS error with ExB Developer Edition and Enterprise

boro — Tue, 13 Feb 2024 15:59:00 GMT

There is a domain name in the FQDN of my laptop (not sharing for obvious reasons), but I can't seem to get node.js to listen to it. Trying to connect to the FQDN + port results in a timeout whereas if i just use the machine name + port it will accept it (but ofc, since i have no domain name in that case, so it's still no help because i can't whitelist it in AGOL). Honestly I'm clueless right now

Re: CORS error with ExB Developer Edition and Enterprise

DougSims_GT — Tue, 13 Feb 2024 16:16:39 GMT

Do you have the domain registered in DNS in your network settings? You should be able to ping your FQDN from the command line successfully.

You say you can't get node.js to listen to it, but your original post mentioned that you didn't have the domain entered into the allowed list (I assume in your portal settings). You can send me a direct message if you want to see if I can provide any more help with specifics (like domain names or IP addresses) that you don't want to post here.

Re: CORS error with ExB Developer Edition and Enterprise

boro — Tue, 13 Feb 2024 16:26:41 GMT

changing localhost to localhost.com in my system32/hosts file did the trick... if only i knew before it was that simple. it's working for me! thanks for the offer of help though 🙂