Skip to main content

Access denied after session is idle

Permanently deleted user
Our users ran into a problem where if they leave a site open but are not active for an hour or so and then try to create a new feature, they encounter the following error:

 

Error: No token available for service https://[servername]/Geocortex/Essentials/REST/sites/[sitename]/map/mapservices/[id]/GeoREST/FeatureServer/[id]/applyEdits

 

I was able to reproduce the problem and once I hit cancel the new feature creation, all of the secured services disappear from the map leaving only the basemap.

 

I don't see anything in the Essentials log files or ArcGIS Server logs that pertain to this issue. Our services are secured using token authentication and the service connection in Essentials reflect that. I've tried to both increase and decrease the short life-span of the token through ArcGIS Server Manager but it doesn't seem to have any effect. We're running GCX Essentials 4.4.0, HTML5 viewer 2.5.0, and ArcGIS Server 10.2. 

 

Has anyone else encountered this?
0

Comments

5 comments

Date Votes
  • Dan Giersz
    We are also having this issue.  Have you made any progress?
    0
  • Dan Giersz
    Can Latitude chime in on this? Is there a way for it to log a user out after inactivity? Or at the very least prompt for a login if the token is missing or invalid?
    0
  • Permanently deleted user
    The viewer should be able to acquire a new token, but it looks like, in your environment, that process is failing. We'll need to take a look at both your client and server requests in order to diagnose this. If you could open a case with the (To: support@latitudegeo.com) Technical Support team, we'll work with you to get to the bottom of this.
    0
  • Permanently deleted user
    Any update on this? we have the same issues, after leaving the site open for a longer period all access to workflows seem to be lost. Only way to get it working again is to refresh the site.
    0
  • Dan Giersz
    Our issue was due to our specific environment.  We had multiple standalone servers that were load-balanced and the load-balancer would bounce traffic to different servers after a period of time.  The tokens were unique to each server, so token errors popped up.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post