topic Re: .NET proxy setup no longer working for WAB Dev 2.4 in ArcGIS Web AppBuilder Questions

.NET proxy setup no longer working for WAB Dev 2.4

BarnabyRockwell — Mon, 27 Mar 2017 22:06:37 GMT

I have been using the proxy setup described by Robert Scheitlin here:

to get around AGOL logins for an internal-only, locally-hosted WAB Dev app that calls an AGOL Web Map. I used username and password authentication. The referenced Web Map is shared with my organization, and is not publicly available.

When I updated the app to WAB Dev 2.4, the proxy setup no longer works, and all I get is a blank (white) browser screen.

App config.json:

"httpProxy":{

"useProxy":true,

"alwaysUseProxy":false,

"url":"/DotNet/proxy.ashx",

    "rules":[{
        "urlPrefix": "http://myorg.maps.arcgis.com/",
        "proxyUrl": "/DotNet/proxy.ashx"
    }]

proxy.config:

<?xml version="1.0" encoding="utf-8" ?>
<ProxyConfig allowedReferers="*"
             mustMatch="true">
    <serverUrls>
        <serverUrl url="http://myorg.maps.arcgis.com"
                   username="username"
                   password="password"
                   matchAll="true"/>
        <serverUrl url="http://services.arcgisonline.com"
                   matchAll="true"/>
        <serverUrl url="http://myinternalserver"
                   matchAll="true"/>
    </serverUrls>
</ProxyConfig>

Does anyone know how I can get the proxy working again? The proxy is still working for my WD 2.3 apps on the same server. I'm running ArcGIS Server 10.5.

Re: .NET proxy setup no longer working for WAB Dev 2.4

BarnabyRockwell — Tue, 28 Mar 2017 21:48:25 GMT

In Firefox, I get this error after loading the app with the proxy:

jimu.js init... main.js:187:7
Load Config: timer startedConfigLoader.js:85
dojo.io.script error Error:
Stack trace:
x/g.error@http://js.arcgis.com/3.20/init.js:984:275
.cache["dojo/_base/xhr"]/</a._ioSetArgs/<@http://js.arcgis.com/3.20/init.js:87:530
c@http://js.arcgis.com/3.20/init.js:103:393
d@http://js.arcgis.com/3.20/init.js:103:182
.cache["dojo/_base/Deferred"]/</a.Deferred/this.errback@http://js.arcgis.com/3.20/init.js:105:163
c@http://js.arcgis.com/3.20/init.js:104:142
d@http://js.arcgis.com/3.20/init.js:103:182
.cache["dojo/_base/Deferred"]/</a.Deferred/this.errback@http://js.arcgis.com/3.20/init.js:105:163
c@http://js.arcgis.com/3.20/init.js:104:142
d@http://js.arcgis.com/3.20/init.js:103:182
.cache["dojo/_base/Deferred"]/</a.Deferred/this.errback@http://js.arcgis.com/3.20/init.js:105:163
.cache["dojo/io/script"]/</b.get/<@http://js.arcgis.com/3.20/init.js:999:98
.cache["dojo/Deferred"]/</n@http://js.arcgis.com/3.20/init.js:107:277
.cache["dojo/Deferred"]/</r@http://js.arcgis.com/3.20/init.js:107:203
.cache["dojo/Deferred"]/</d/this.reject@http://js.arcgis.com/3.20/init.js:109:488
.cache["dojo/Deferred"]/</b@http://js.arcgis.com/3.20/init.js:108:172
.cache["dojo/Deferred"]/</n@http://js.arcgis.com/3.20/init.js:107:450
.cache["dojo/Deferred"]/</r@http://js.arcgis.com/3.20/init.js:107:203
.cache["dojo/Deferred"]/</d/this.reject@http://js.arcgis.com/3.20/init.js:109:488
.cache["dojo/Deferred"]/</b@http://js.arcgis.com/3.20/init.js:108:172
.cache["dojo/Deferred"]/</n@http://js.arcgis.com/3.20/init.js:107:450
.cache["dojo/Deferred"]/</r@http://js.arcgis.com/3.20/init.js:107:203
.cache["dojo/Deferred"]/</d/this.reject@http://js.arcgis.com/3.20/init.js:109:488
.cache["dojo/Deferred"]/</b@http://js.arcgis.com/3.20/init.js:108:172
.cache["dojo/Deferred"]/</n@http://js.arcgis.com/3.20/init.js:107:436
.cache["dojo/Deferred"]/</r@http://js.arcgis.com/3.20/init.js:107:203
.cache["dojo/Deferred"]/</d/this.reject@http://js.arcgis.com/3.20/init.js:109:488
.cache["dojo/Deferred"]/</b@http://js.arcgis.com/3.20/init.js:108:172
.cache["dojo/Deferred"]/</n@http://js.arcgis.com/3.20/init.js:107:450
.cache["dojo/Deferred"]/</r@http://js.arcgis.com/3.20/init.js:107:203
.cache["dojo/Deferred"]/</d/this.reject@http://js.arcgis.com/3.20/init.js:109:488
g/<@http://js.arcgis.com/3.20/init.js:1005:204
.cache["dojo/on"]/</n.once/f<@http://js.arcgis.com/3.20/init.js:122:420

Re: .NET proxy setup no longer working for WAB Dev 2.4

CCWeedcontrol — Fri, 31 Mar 2017 17:10:10 GMT

Did you ever find out what was wrong with your proxy?

I am having the same issue with WAB 2.4. Proxy worked fine in WAB 2.3 but now i get

This the error i get from proxy

"error":{"code":403,"messageCode":"GWM_0003","message":"You do not have permissions to access this resource or perform this operation.","details":[]}}

I made sure everything is set up properly. I followed the instructions here but no luck.

Re: .NET proxy setup no longer working for WAB Dev 2.4

BarnabyRockwell — Fri, 31 Mar 2017 17:17:23 GMT

Unfortunately, I still have no idea what the problem is.... Robert S. wrote that he may look into the issue soon....fingers crossed.

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Fri, 31 Mar 2017 17:55:18 GMT

Well the bad news guys is that I just tested a 2.4 app that uses a secure service and configured my proxy.config with the username and password and I don't have any issue.

Re: .NET proxy setup no longer working for WAB Dev 2.4

CCWeedcontrol — Fri, 31 Mar 2017 18:07:29 GMT

Robert thanks for looking into this. Can you post the httpProxy in the config.json and the and proxy.config you are using. I am lost on why it doesn't work on 2.4.

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Fri, 31 Mar 2017 18:54:35 GMT

Mine is much the same as what Barnaby posted except that I am using a secure map service and not a secure web map. So my proxy.config serverUrl point to my ArcGISServer url and not my orgs AGOL url.

Re: .NET proxy setup no longer working for WAB Dev 2.4

CCWeedcontrol — Fri, 31 Mar 2017 19:11:23 GMT

I figured out what what wrong with mine. No sure if its the same problem you have but after looking at my Chrome network in developer tools i noticed that my proxy was getting stuck at' proxy.ashx?https://****.maps.arcgis.com/sharing/rest.. '

in my proxy config i had http://***.maps.arcgis.com, my proxy config file did not have 'https'. once i changed http to https in the proxy config it worked. Not sure why it's https. When i set up WEB 2.4 I put both http and https. My developer page shows my url as http not https.

I checked my 2.3 apps in Chrome network developer tools and the proxy is proxy.ashx?http://****.maps.arcgis.com/sharing/rest and that's why i had on my proxy config.

Not sure why it changed...?

anyway after 5 hrs of trouble shooting, hopes this helps.

Re: .NET proxy setup no longer working for WAB Dev 2.4

BarnabyRockwell — Fri, 31 Mar 2017 19:33:18 GMT

Yes! That was it. WD 2.4 apps require https in both the config.json and the proxy.config for the AGOL URL.

WD 2.3 apps require http, and will not work with https as far as I can tell.

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Tue, 09 May 2017 17:09:47 GMT

I am getting a similar problem, I get the error "Unable to get property 'indexOf' of undefined or null reference" with a sad face. Not sure what I could be doing wrong, I have the WAB application shared to Everyone in AGOL, the layer and map shared with the organization, and I've done this setup for proxy several times. I've been trying just about everything for the last few weeks with no results. My code is as follows:

Proxy.config:

<?xml version="1.0" encoding="utf-8" ?>
<ProxyConfig allowedReferers="*"
             mustMatch="true">
    <serverUrls>
        <serverUrl url="https://tog.maps.arcgis.com"
  username="<uname>"
  password="<pw>"
        matchAll="true"/>
<serverUrl url="https://services.arcgisonline.com"
  matchAll="true" />
<serverUrl url="https://gissvr"
  matchAll="true" />
    </serverUrls>
</ProxyConfig>

json.config for the app:

"httpProxy": {

"useProxy": true,

"alwaysUseProxy": false,

"url": "http://gissvr/DotNet/proxy.ashx",

"rules": [

{

"urlPrefix:":"https://www.tog.maps.arcgis.com",

"proxyUrl":"/DotNet/proxy.ashx"

}

]

}

(gissvr is the name of the internal web server)

I've tried this with both clientid/secret and username/password, no change in results.

I tried setting all urls to https (not just AGOL ones), no change.

I have also tried hosting the app on my external web server, and setting this all up there (with the external ws name), and I have the same results there as well.

Is there something that I might not be looking at? I've been through the documentation from ESRI, github, stackexchange, etc., to no avail.

I am just now starting with web appbuilder, so I didn't come from 2.3 version, so I can't say this was broken by 2.4.

Thank you for looking at this...

Jeff

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Tue, 09 May 2017 17:34:23 GMT

Jeff,

Mixing http and https is not a good thing to do (but I see you mentioned you already tried setting all urls to https). You should change your urls to https again and leave it that way. Your url to your proxy server is the internal machine name gissvr you should use the external machine name. Have you tested your proxy using http://gissvr/DotNet/proxy.ashx?ping

I also notice in your config.json file you have the proxy rule urlPrefix set to https://www.tog.maps.arcgis.com (it should not have "www").

Does you app function properly if you set the useProxy to false (meaning you have to login, but you do not get the error)?

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Tue, 09 May 2017 20:29:08 GMT

Hi Robert,

Thanks for replying. I did set the urls all back to https, and I fixed the url that had the www in it (the agol one). I still am getting the error.

I set useproxy to false, and it works, I get the login box.

When I ping the page I get { "Proxy Version": "1.1.1-beta", "Configuration File": "OK", "Log File": "Not Exist/Readable"}

We have an internal server (gissvr is the alias) that I host our internal apps on, and an external server (www.gilbertmapping.com<http://www.gilbertmapping.com>) that has a web adaptor that is connected to gissvr. I put the proxy on both machines, as I’m not sure which one it uses. I changed the url in the config.json to use the external server, so I would assume that it is now using the proxy.config on the external server.

I had also tested hosting the app on the external server, and using the proxy on the external server. That way the internal server wasn’t even a part of it all. I still get the same error though.

Thanks,

Jeff

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Tue, 09 May 2017 20:34:09 GMT

Jeff,

If everything is on the external server now can you provide the url so I can test?

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Tue, 09 May 2017 21:17:44 GMT

Hi Robert,

The url is below:

http://www.gilbertmapping.com/wab/DevAgreements/index.html

Thanks,

Jeff

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Sat, 11 Dec 2021 09:20:24 GMT

Jeff,

In the SelectionManager.js You seem to have made some chenages and introduced a major syntax error:

define([
    'dojo/_base/declare',
    'dojo/_base/Deferred',
    'dojo/_base/lang',
    'dojo/_base/array',
    'dojo/topic',
    'esri/layers/FeatureLayer',
    'esri/layers/GraphicsLayer',
    'esri/geometry/geometryEngine',
    'esri/graphic',
    'esri/Color',
    'esri/symbols/SimpleMarkerSymbol',
    'esri/symbols/Sinew SimpleLineSymbol(lineSolidStyle, Color.fromArray([0, 255, 255]), 2);‍‍‍‍‍‍‍‍‍‍‍‍‍

line 13 and following is the issue above:

define([
    'dojo/_base/declare',
    'dojo/_base/Deferred',
    'dojo/_base/lang',
    'dojo/_base/array',
    'dojo/topic',
    'esri/layers/FeatureLayer',
    'esri/layers/GraphicsLayer',
    'esri/geometry/geometryEngine',
    'esri/graphic',
    'esri/Color',
    'esri/symbols/SimpleMarkerSymbol',
    'esri/symbols/SimpleLineSymbol',
    'esri/symbols/SimpleFillSymbol'
  ],
  function(declare, Deferred, lang, array, topic, FeatureLayer, GraphicsLayer, geometryEngine,
    Graphic, Color, SimpleMarkerSymbol, SimpleLineSymbol, SimpleFillSymbol) {
    var instance = null;

    var clazz = declare(null, {

      constructor: function(){
        if(window.isBuilder){
          topic.subscribe("app/mapLoaded", lang.hitch(this, this._onMapLoaded));
          topic.subscribe("app/mapChanged", lang.hitch(this, this._onMapChanged));
        }else{
          topic.subscribe("mapLoaded", lang.hitch(this, this._onMapLoaded));
          topic.subscribe("mapChanged", lang.hitch(this, this._onMapChanged));
        }
      },

      /**
       * The display layers(GraphicsLayer) for layer in mapService. The display layer is used for show highlight.
       * For feature layer in map, we don't need display layer because the feature layer will show the highlight.
       * @type {Object}
       */
      _displayLayers: {},

      setSelectionSymbol: function(layer){
        var type = layer.geometryType;
        var markerCircleStyle = SimpleMarkerSymbol.STYLE_CIRCLE;
        var pointSymbol = new SimpleMarkerSymbol(markerCircleStyle, 16, null, Color.fromArray([0, 255, 255]));

        var lineSolidStyle = SimpleLineSymbol.STYLE_SOLID;
        var lineSymbol = new SimpleLineSymbol(lineSolidStyle, Color.fromArray([0, 255, 255]), 2);

        var fillSolidStyle = SimpleFillSymbol.STYLE_SOLID;
        var fillSymbol = new SimpleFillSymbol(fillSolidStyle, lineSymbol, Color.fromArray([0, 255, 255, 0.3]));

        if (type === 'esriGeometryPoint') {
          layer.setSelectionSymbol(pointSymbol);
        } else if (type === 'esriGeometryPolyline') {
          layer.setSelectionSymbol(lineSymbol);
        } else if (type === 'esriGeometryPolygon') {
          layer.setSelectionSymbol(fillSymbol);
        }
      },‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

You should probably just restore the SelectionManager.js from the stemApp.

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Wed, 10 May 2017 13:50:47 GMT

That’s odd. I didn’t edit that file, I had to search for it even, I never knew it was there (unless I made a change to a widget that updated that file somehow, but I thought widgets were self contained). Anyway, I copied over the original SelectionManager.js file from the stemapp of the wab install folder. Now the internal one does not get the error (the proxy doesn’t work either, I get a login box, I made sure I set useProxy back to true after testing yesterday). However, the external one still gets the same error. I replaced the file in both deployments.

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Sat, 11 Dec 2021 09:20:27 GMT

Jeff,

Syntax errors are killing you right now. Here is your next issue in the apps config.json:

  "httpProxy": {
    "useProxy": true,
    "alwaysUseProxy": false,
    "url": "https://www.gilbertmapping.com/DotNet/proxy.ashx",
    "rules": [
      {
        "urlPrefix:":"https://tog.maps.arcgis.com",
        "proxyUrl":"/DotNet/proxy.ashx"
      }
    ]
  }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Line 7 you have "urlPrefix:":"https://tog.maps.arcgis.com", and it should be:

  "httpProxy": {
    "useProxy": true,
    "alwaysUseProxy": false,
    "url": "https://www.gilbertmapping.com/DotNet/proxy.ashx",
    "rules": [
      {
        "urlPrefix":"https://tog.maps.arcgis.com",
        "proxyUrl":"/DotNet/proxy.ashx"
      }
    ]
  }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Wed, 10 May 2017 14:37:35 GMT

Hi Robert,

Good catch. I always miss these things, that’s a big part of what makes js difficult for me. David had also mentioned that I could have missed something like that. I’m surprised tech support didn’t see that.

I still get the same results though…

Re: .NET proxy setup no longer working for WAB Dev 2.4

RobertScheitlin__GISP — Wed, 10 May 2017 15:05:35 GMT

Jeff,

I don't get the white screen, frowny face error anymore. I just get the login dialog now. When I look at the network traffic I see that the request to your portal through your proxy has an error of "Invalid Token". This means that your provided credentials in the proxy.config are not correct.

Re: .NET proxy setup no longer working for WAB Dev 2.4

JeffSauder — Wed, 10 May 2017 15:12:23 GMT

Hi Robert,

I did try the external one on a different machine, and I got the same as you did. I will check my credentials. Should I be using the client ID or the username for the service?

Also, how did you discover the SelectionManager.js had bad syntax? I never saw that come up in anything I ran (fiddler, f12 dev tools). That kind of stuff worries me, that a simple change could possibly break the whole thing.