As some users before, our team was experiencing problems with WebAppBuilder and ArcGIS Portal login, once nodejs was already initiated and portal url was verified successfully. Our users credentials were never validated and we were unable to login (incorrect username or password message). We recently found out that it was due to some kind of compatibility issue with our corporative http proxy.
Does anyone know how to configure WebAppBuilder to work behind a corporative http proxy? Thanks!
Solved! Go to Solution.
Thanks for providing the information.
Could you please describe what is your office network environment? What kind your proxy is or the steps to setup your proxy network? So we can reproduce your problem and find a workaround.
AFAIK, due to the fact that we are not the network administrators, we are behind a http(s) proxy which captures all mentioned traffic to the Internet being itself who finally sends/gets the contents, making first a filter of the contents asked and evaluating if they are convenient for the environment we are in.
So, in any application who needs access to the Internet, it is mandatory to configure this proxy to access any content. I.e. configuring it on Internet Explorer (or whichever browser you use) under the label “Connections”à LAN Settings à Proxy Server.
With this firewall/proxy deployment, there is no machine except the proxy server who has http(s) access. While the traffic is sent via Chrome, we can access arcgisonline as the proxy is configured in the browser, but, we have sniffed http traffic by application and we noticed that the web app builder sends traffic by itself (the server mounted) so it cannot access the Internet, with the result of not being able to validate our application on arcgisonline.
Thanks. Best regards.
First of all, I think you have made a mistake in the code. After putting your proxy you have forgotten to add a comma (",") at the end of the line (in both types of requests - lines 36 and 45), therefore a SyntaxError message is shown in command window.
Besides, I don't know how you have your network configured but maybe you should have to write your whole http proxy server URL. For instance, in our case, we had to write it with the protocol and port as well: