Public Web App Deployed onto Server Still Calls for Login

07-12-2018 01:54 PM
New Contributor III


I have a web app that I created using WAB Dev. I am on a single machine deployment of Enterprise installed using the Enterprise Builder where Server and Portal are federated. After configuring the app, I downloaded the zipped app file, unzipped it into the www folder on the web server and added the application in IIS, added the app to Portal, and then put the app id into the config.json file of the app. 

Even though EVERY feature layer, basemap layer, the web map itself, and the web app are shared to everyone, and the organization allows for anonymous access, I still get prompted for a login. I have a few ideas of what it could be, but I'm at a loss here because this hasn't happened before. 

1) I have two or three widgets (coordinate conversion, share, and about) on the app that I did not have prior to using the WAB Dev edition. The organization doesn't have an arcgis online account, so if any of those widgets are considered 'premium' that may be the issue. 

2.) I did not add a proxy to the proxy property in the config.json file, as the Esri Support Analyst I spoke to said it wasn't necessary because of my current configuration. I also haven't registered the app yet. The test app I made using WAB Dev did not require a login to view, despite not being registered or having the proxy. However, it was much simpler than the current app I am working on.

Here is the code for the Proxy Property in the config.json file:

"wabVersion": "2.8",
"isTemplateApp": true,
"isWebTier": false,
"httpProxy": {
"useProxy": true,
"alwaysUseProxy": false,
"url": "",
"rules": []

3)  I have pictures in the about widget, and a picture in the app of the organization logo. When I created a web app previously using the Portal Webapp Builder, I never had issues making the application public even though I had the organizational picture in the app. Do I need to upload every picture in my app to the server/portal?

4) I have a few basemaps that are from Esri. I really don't think this is the reason though, as I have never had this problem when using them previously. 

Any help would be greatly appreciated, as I am truly at a loss. 

0 Kudos
4 Replies
MVP Emeritus


   I don't have any experience deploying a WAB app to a federated Portal, but my advice would be to look in your browsers network tab and look for any 4xx errors and see what is failing because of authentication and that may give you a better clue.

New Contributor III

Hi Robert, 

I looked in the network tab, and did not see any 4xx errors, but I did notice something that may be confirmation enough to know that it's a proxy issue. I noticed I was getting a "Cross-Origin-Request Blocked" for the few basemaps I have that reference tiles hosted on "". 

I also found That the portal is supposed to act as the proxy server when needed. However, in my Portal Admin Security Configuration, I do not have any "allowedproxyhosts":  listed. 

Also, in the config.json file for the app, the "authorizedcrosOriginDomains": line is blank as well. 

What would be my best course of action? Inserting [] into the "authorizedCrossOriginDomains": line in the config.json file?



0 Kudos
MVP Emeritus


   As I mentioned I do not use Portal so I can only speculate. You would be better off opening a ticket with esri tech support.

0 Kudos
New Contributor II

Hi Steven,

Did you end up having a solution to this issue? We're having a very similar problem with one of our Apps, everything is listed as "shared to public" yet Portal keep's asking for a log in. Did you end up editing the config file?



0 Kudos