Latest Contributions by danbecker

Same problem here, latest ver. of iOS on iPad and it crashes when submit is pressed. I'm using offline map, Collector and server are both ver. 10.3. The offline map includes: a cached map service built using esri basemap tiling scheme also enabled tile exports on the service Feature service is non-versioned SDE feat. classes that have archiving and attachments enabled. Both the cached map service and feature service are proxied, (added as items to AGOL, service credentials *not* stored with the item). If I understand correctly, the cached (tiled) map service is causing the crash? Android works fine. thanks. ... View more

I just tested the latest version of ArcGIS for AutoCAD plugin with AutoCad Civil 3d 2015. Secured services from 10.3 ArcGIS Server are not accessible using the plugin. When adding the ArcGIS Server connection and providing credentials in AutoCAD you get an "Error 405 Method not available" or similar, I can't remember the exact text. I started Fiddler and captured the token request when attempting to sign into Server from Autocad and the plugin is sending a http GET request. This is not compatible with ArcGIS Server 10.3, according to this doc: Acquiring ArcGIS tokens—Documentation | ArcGIS for Server.‌ At the top of that doc, it says "HTTP POST token requests must have username/pw passed in the body of the request, and HTTP GET requests are not supported." So, it looks like 1 of 3 things has to happen before the latest ArcGIS for AutoCAD plugin will work with Server 10.3 token secured services. 1. the ability to enable http GET requests on Server 10.3. I only found documentation to disable http GET, which doesn't really make sense if it is disabled by default, according to the above doc? Disabling token acquisition through HTTP GET requests—Documentation | ArcGIS for Server.  I tried setting "allowHttpGet": "true" in ArcGIS Server admin, but it didn't work. 2. The plugin needs updating so it sends a token request via http POST 3. Write a custom proxy to intercept the plugin's GET request, obtain a token from the server using a POST request, and relaying everything back to the plugin. Likely more trouble then it's worth. This is the 2nd annoying authentication issue in 10.3 I've found. ESRI, can you please update us? thanks. ... View more

So you added a secured feat. Service and stored credentials, then downloaded map in collector? Can you msg me, I will give you my rest URL and credentials to try. I have been trying with the top level URL, copied directly from browser. I also reprpduced the feature service link displaying 403 error when I used esri's sample server6, but since that service wasn't sync enabled couldn't test collector download. ... View more

nothing in arcgis server logs. Yes, this is happening on both iOS and android collector apps. Going a step backward, there is a way to "test" if the secured service will work in Collector, prior to adding the service item to a webmap. In the above workflow, right after step #9, you will be at the item details page, that summarizes the service item you just added to ArcGIS Online. At the top of the page, just to the right of the thumbnail image, click on the "Feature Service" hyperlink. If you get Error 403 you do not have permission, then this feature service layer WILL NOT be downloadable in Collector. Conversely, if you are properly redirected to the Feature Service REST endpoint page, then the service layer WILL be downloadable in Collector. Again, the behavior of the Error 403 page, and subsequently not being able to download the layer in Collector are BOTH related to storing credentials with the layer when adding it to ArcGIS Online. This bug, or lack of documentation is causing us issues. All field crews have to remember, both their ArcGIS Server AND ArcGIS Online credentials. Not to mention the fact you're continually typing in credentials every time you try and access the secured service. ... View more

we have server 10.3, and I was unable to sync attachments from iOS to a feature service that was versioned in SDE. Follow this workflow, I bet sync with attachment will work. 1. create new SDE geodatabase, feat. dataset and feat. class 2. add globalIDs 3. enabled archiving 4. enable attachments 5. publish service with sync enabled 6. add feat. service as item in Arcgis.com, DO NOT store credentials with the item if service is secured. BUG-000084538 was logged yesterday. Support helped me to determine storing credentials with secured services when added to arcgis.com was causing issues with collector. 7. create webmap with your newly added item 8. share both service and webmap 9. take offline with collector, create points, take photos with camera 10. sync. 11. this workflow works every time, no issues. Key items: NO versioning, NO storing credentials. ... View more

dbecker88 if I may ask you or others: I'm trying for the first time to set up security. We have one service we want to use with tokens. Just http for now. (https later). We set up SQL database with some users and roles and enabled anonymous user roles. I turned it to http following the docs - http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#/Setting_up_users_and_roles_in_SQL_Server/0093000000q0000000/ <Web server root>\ArcGIS\Tokens\web.config and other two files updated fine. Note.. there was no space in the second key line, make sure to check spaces pasting in the AppSettings keys! We turned on the token service. I can get to our token service page fine with http://ourserver/tokens/gettoken.html That generates a token fine. However in our site and on the sample Sandbox (http://developers.arcgis.com/en/javascript/sandbox/sandbox.html?sample=widget_identitymanager_client_side)    ... the user / role we created for this Service fails. I included Identity Manager and the local storage stuff from the sample (we want local storage for now, maybe proxy later..) It pops up as it should, asks for credentials. But when I enter the user /pass it says "Unable to access the authentication service. " However... when I turn the service Permissions in ArcGIS Server Manager to "Everyone" it works just fine! Interestingly though I noticed this secure service half-works on ArcGIS.com. I spied on it in F12/Firebug network connections and saw it got a token (the token at the end of the URL).  However popups do not work. Even with everyone access. But that is fine, popups work with Everyone access in our site. It's only when we lock it down to the secured User that it fails, "Unable to access the authentication service." Anyone seen this? Called tech support, we couldn't fix it, we tried making a new user, new service/.msd, etc. Still happens. In fact I took the sample, but just stuck my secured service in it, same error. As both FeatureLayer and Dynamic. Will keep working on it, post results back... trying to remember back to server 10....we also really struggled with the initial setup of sql users/roles. IMO, if you have the ability, upgrade to 10.1 and scrap sql users/roles. The integrated 10.1 user/role store is 100% easier and doesn't require sql. When we upgraded, I ended up having to re-enter 100's of users into the integrated 10.1 security store, but it was well worth it IMO. The 10.1 manager is also 100% better. Back to 10...are you able to successfully connect to sql database in manager? When you assign a role to your service, (i can't remember exact steps) but we had 2 locations that roles were displayed, local and domain **i think**. If we added the role from one, it wouldn't work, but from the other it did. This was because the GIS server was also a AD domain server. this isn't a JS problem, it's a server 10 .NET config issue ... View more

And if it's OK I'll jump on this bandwagon -- anyone using server-side authentication with ESRI secured REST services, via ASP.NET, and have it up as a site we could check out? So, instead of a second popup for credentials it just uses the ones you already provide if you log in to the standard Windows Forms ASP.NET site (with the Log In on Site.Master and SQL Server database backend functionality). We have API 3.4 with Arc 10.0 Sp5 secured REST service now. We are testing with Identity Manager but it'd be nice to piggyback on the built-in ASP.NET authentication mechanism. I guess in referring to this http://help.arcgis.com/en/webapi/javascript/arcgis/jshelp/ags_secureservices.html it may (does?) involve a proxy page? Haven't played with those, we've attempted to stay away from it until we really need it. If we figure this out we'll post back here, too. In a round-about way we're in the process of doing something similar. Rather then a 100% custom solution, we are still using the built-in esri Token security mechanism. This is all for a one-time login. If the user originates from an "already secured site" they have permission to view the js app. But, we dont' have access to the "already secured site's" auth. mechanism. So, here's how we handle it. external site--> server out of our control     user clicks link to js app--> server out of our control     jquery ajax fires call to .ashx handler--> server out of our control         server side .ashx handler grabs client IP--> server out of our control         .ashx handler sends client IP to ourServer.php script via url post--> our server                 -ourServer.php checks ip of incoming call,                 -if from accepted IP, requests a token from the GIS Server using hard-coded creds.                 -stores token, client IP and random gen. key in sql db                 - returns random key to .ashx handler         .ashx handler returns key to ajax success handler-->server out of our control     jquery appends key to js app link href attribute-->server out of our control js app checks for key when the user arrives at site--> our server     -if a key is found, the proxy.php page query's sql db, and retrieves the previously stored token using the key and client IP     -if key and client IP match, return token to js app js app loads token using the same method here: http://help.arcgis.com/en/webapi/javascript/arcgis/jssamples/widget_identitymanager_client_side.html     -if the token is valid and not expired, the identityManager will handle the credential and not prompt for login if for some reason the https://oursite/jsLInk?key=aRandomstring is emailed to a dif. user, and they try the link within 60mins (token expiration) of when the orig. user clicked on js app link, it won't work because the proxy.php script on our server wont' retrieve the token from sql db because client2 has a dif. IP as what's associated with the key that client2 is passing ... View more

Just having a look at the identity manger for securing services - http://help.arcgis.com/en/webapi/javascript/arcgis/jsapi/identitymanager.html And wondered if anyone has done much customisation around this and how to do it e.g. Change to jQuery popup, changing text that appears in login popup, don't show again checkbox? Cheers 🙂 haven't swapped out the dialog, but I did change the text by adding this to init function. If you do customize text, make sure and maintain the ${server} and ${resource} params, otherwise the dialog doesn't work. esri.bundle.identity.info = "If you have not received a login, please contact this person. <br><br>[email protected] ${server} ${resource}"; ... View more

workaround: the only way I knew of detecting whether the stored token was invalid was to send an esri.request to the service. If the error callback gets fired the token is either invalid or expired. At this point, the user needs to log in regardless, so just to be sure the identityManager calls the tokenServiceURL, we manually edit the stored token to be expired then refresh the state of the identityManager so it prompts for signIn. function loadCreds() { var def = new dojo.Deferred(); var idJson, idObject; if (supports_local_storage()) {   idJson = window.localStorage.getItem(credential); } else {   // read from a cookie   idJson = dojo.cookie(cred); } if (idJson && idJson != "null" && idJson.length > 4) { //proceed with loading credential   idObject = dojo.fromJson(idJson);   var token = idObject.credentials[0].token; //token that was stored   //query used to test if loaded token is valid   var url = "https://mygis.server.com/arcgis/rest/services/folder/service/MapServer/0/query";   var req = esri.request({    url : url,    content : {     where : "aField='aValue'",     f : "json",     token : token    }   }, {    useProxy : false   });   function success(data) {    esri.id.initialize(idObject);    def.resolve("valid token loaded");     }   function error(error) {    idObject.credentials[0].expires = 0000; //manually edit the loaded cred expireDate so the identityManager properly calls tokenService URL for new token    esri.id.initialize(idObject);    def.resolve("token invalid or expired");   }   req.then(success, error); } else{   def.resolve("not loaded"); } return def.promise; } var firstProcess = loadCreds(); firstProcess.then(function(loadCredResults){//wait for stored credentials to load         return secondProcess(); }).then(function(secondProcessResults){//wait for the secondProcess         finishInit(); }); ... View more

confirmed; if you set the "expires" value for the credential in localStorage to to a past timestamp, then browse to the app, the credential is loaded from storage, identityManager signIn dialog appears, and you can sign in normally. i.e. The tokenServiceURL is called like it should be. So, why isn't the tokenServiceURL called when the token in storage is invalid and not expired? Why does the stored token get corrupted, obiv. outside of manually corrupting it? ... View more