nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Invalid Token for QueryTask

MostafaAsadi

Hi,

I have a secure Map Server that I can access by typing its url and token in the address bar of my browser: http://serverurl?token=token_value. However, when I call a QueryTask, I get an "Invalid Token" error:

{"code":498,"message":"Invalid token","details":[]}

Here's how I construct and run the QueryTask:

var url = "http://serverurl?token=token_value";
var task = new esri.tasks.QueryTask(url);
var q = new esri.tasks.Query();

// set query parameters ....

task.execute(q, callbackHandler);

Can someone point out to me the possible cause for this error?

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

MostafaAsadi

We have used the Sample JavaScript Viewer as template for our work and now upgrading to v2.8 is going to be painful, especially that I have no idea what needs to change.

derekswingley1

2.8 identity manager works great for secure services, even if the service is used for find/query.

someone correct me if I'm wrong, but the only change to your code is to add:
dojo.require("esri.IdentityManager");
var facils = new esri.layers.FeatureLayer("https://mydomain.com/ArcGIS/rest/services/secured/0",{
    mode:esri.layers.FeatureLayer.MODE_ONDEMAND,
    outFields:["*"]
});

That's great! And yes, that's all you need to do in your code to use the identity manager. What's stopping you from upgrading to 2.8?

danbecker

Mo, have you done a test with api 2.8 ?

2.8 identity manager works great for secure services, even if the service is used for find/query.

someone correct me if I'm wrong, but the only change to your code is to add:

dojo.require("esri.IdentityManager");
var facils = new esri.layers.FeatureLayer("https://mydomain.com/ArcGIS/rest/services/secured/0",{
    mode:esri.layers.FeatureLayer.MODE_ONDEMAND,
    outFields:["*"]
});

nicogis

Mo, have you done a test with api 2.8 ?

derekswingley1

But like I mentioned, typing the url+token in the browser authenticates with no issues. If the token was expired I wouldn't be able to open up the url in the browser. Btw I'm using the JavaScript API v1.2 if that makes a difference.

We've greatly simplified how secure services are accessed by introducing the identity manager at version 2.5. My recommendation is to upgrade your app to at least 2.5 (preferably you would upgrade to the latest version, which is 2.8) and use the identity manager to handle tokens for you.

GeorgePan

Did you fix it?

MostafaAsadi

But like I mentioned, typing the url+token in the browser authenticates with no issues. If the token was expired I wouldn't be able to open up the url in the browser. Btw I'm using the JavaScript API v1.2 if that makes a difference.

Thanks.

nicogis

the token can be also expired with error 498.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.