After the update to ArcGIS Enterprise 11.5 we have problems with invalid tokens. When loading a webmap no data is shown and in the browser DevTools network tab we see an endless stream of requests.
We hoped that this would be solved with the 11.5 Web Applications Patch. We installed is as soon at it came out. It seemed to solve the issue for a week or two.
But since august 19th suddenly similar problems came back. We did not change anything in the configuration. But this time we did not receive chunk errors. But we have an endless stream of requests (a repetition of generatetoken request followed by a featureserver or mapserver request) the mapserver request shows the error 'Invalid Token'.
And we also discovered that we can not login to server manager (/arcgis/manager) via the webadaptor, only direct via the port number :6443/arcgis/manager.
This is what we analyzed about the requests generated:
The token generated by portal/sharing/rest/generatetoken is used to go to an arcgis/rest/server service, f.e. arcgis/rest/server/FeatureServer
The respons of the FeatureServer request is that the just generated token is invalid.
Do these two endpoints use the same sharedKey to eigther generate the token or check if it is valid?
If so, where can I find the sharedkey each of the endpoints is using? Although it seems strange that this key is changed overnight
If not what could then be the problem?
What we already tried:
- Turning off SNI, which binds :443 to 0.0.0.0 instead of the domain name. --> no change, turned it back on again
- Tried again the prelimanary fix for the 11.5 upgrade cache issues (https://community.esri.com/t5/arcgis-enterprise-portal-questions/content-failing-to-load-completely/... --> no change, turned it back again
- Reinstalled the Portal for ArcGIS 11.5 Web Applications Patch + cleared browser caches
- Updating the sharedkey of portal and re-registered the webadaptors.
- Manually, with postman, performed the generatetoken request and the request to the arcgis/rest/server/FeatureServer endpoint with the received token --> also returned the Invalid token error
- Reinstall Portal.
Does anyone recognise this behaviour and more important; did anyone find a solution?
