Latest Contributions by JohnGravois

glad to hear it Daniel.  thanks for taking the time to recap. ... View more

my usual technique of snooping more deeply is to run the proxy in a custom application pool with my own credentials.  that way a tool like fiddler will capture not only the request 'to' the proxy, but also the request that the proxy itself is making. ... View more

if you've paid for an associated product you can email support@esri.com or call 888.377.4575 with your customer number to log a new call requesting help with our javascript api. in general, you need to forget about using appId/appSecret and figure out why username/password aren't sufficient when attempting to load a private webmap with only a single public basemap layer.  most importantly, when you snoop the web traffic generated by your app, does the request to retrieve the JSON describing the webmap go through the proxy at all? ... View more

only 90% sure i understand the whole use case, but it sounds like registering the app and getting an appId and appSecret isn't doing anything for you here. if you are exclusively trying to access a private webmap with private services, username/password for the secure items only in the proxy.config should be sufficient. i don't think it would hurt to log a tech support ticket for this.  it might be easier to hash out over the phone anyway 🙂 ... View more

thats fine.  you can tell them you'd like to work with me specifically if you want 🙂 appId/appSecret should not be thought of as a way to authenticate and access shared content.  those credentials are specifically intended to allow an application to access subscription services which burn credits without requiring someone to sign in, or provide information to identify an app which uses an OAuth2 technique to have people sign in with their own credentials to work with private content. ... View more

if your hosted service is shared publicly, don't include appId/appSecret or username/password in within the <serverUrl> item. if the service is only shared with your org or a specific group, use username/password (and not appId/appSecret) <serverUrl url="https://services2.arcgis.com/gGQziFjRK38YOiW5/arcgis/rest/services"    username="USER"   password="PW"   rateLimit="600"   rateLimitPeriod="60"   matchAll="false"> </serverUrl> ... View more

are you using https across the board? (ie: to load the application itself, to load all supporting CSS and JS and all map resources) ... View more

you can set permissions on individual items (that you own) in ArcGIS Online by navigating to their item details page and clicking "share" [ATTACH=CONFIG]34341[/ATTACH] http://esrihack.maps.arcgis.com/home/item.html?id=a3e05a39087c4a768d43ae231ea158e0 ... View more

are your own REST services public or do they require authentication? if so, are you including the credentials for that specific resource in the proxy.config? if you try to use the proxy directly in the browser to access the REST endpoint is it successful? ie: http://yourmachine/folder/proxy.ashx?http://services2.arcgis.com/arcgis/blah.... ... View more

glad to hear i was able to help sort you out.  you'll want to use either http or https across the board for resources and your actual application to avoid mixed protocol errors thrown by the browser. ... View more

sorry guys, i totally botched that one. ... View more

yup.  mustMatch="true" causes the proxy to compare the request to the whitelist in the proxy.config.  if the url stub is not an exact match, it will throw an error rather than fetch the page and hand it back to you. from what i saw before, you had 'arcgis.com' but not 'www.arcgis.com'. ... View more

Daniel, if you snoop the web traffic when you launch your application you should see that a request to retreive the private webmap json is specifically whats failing. http://www.arcgis.com/sharing/rest/content/items/cd23069c1aeb44f79e072932d30bccac/data?f=json this can be resolved by adding the following serverUrl tag to your proxy.config. <serverUrl url="http://www.arcgis.com"             username="john"             password="doe"                        matchAll="true"> </serverUrl> after updating your proxy.config, try adapting this sample (i just confirmed it works fine) <!DOCTYPE html>   <html>   <head>   <title>Create a Web Map</title>   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">   <meta name="viewport" content="initial-scale=1, maximum-scale=1,user-scalable=no">   <link rel="stylesheet" type="text/css" href="http://js.arcgis.com/3.8/js/esri/css/esri.css">   <style>     html,body,#mapDiv,.map.container{       padding:0;       margin:0;       height:100%;     }   </style>   <script>var dojoConfig = { parseOnLoad:true };</script>   <script src="http://js.arcgis.com/3.9compact/"></script>   <script>     require([       "esri/map",       "esri/arcgis/utils",       "esri/urlUtils",       "esri/config",       "dojo/domReady!"       ], function (Map, arcgisUtils, urlUtils, esriConfig) {                 //define proxy rule                urlUtils.addProxyRule({           proxyUrl: "/sproxy/proxy.ashx",           urlPrefix: "www.arcgis.com/sharing/rest"         });                 //swap for your own private webmap         arcgisUtils.createMap("cd23069c1aeb44f79e072932d30bccac", "mapDiv");     });   </script>   </head>   <body>     <div id="mapDiv"></div>   </body>   </html> ... View more

require([" "esri/map",esri/dijit/LocateButton", "esri/dijit/HomeButton" ], function (Map, LocateButton, HomeButton){ ... View more