How to set default token length of a secure app?
Répondu
Is there a way to set the default token length on an app level? We are running into issues with the current token length. It seems Web is using a 30 minute token length - this is different than our Portal's default.
The issue we are facing, users will leave the app up - in a separate tab - without interaction for longer than 30 minutes. This causes the token to expire but Web seems to have issue refreshing the token without users interacting with the app. Below is a console of the error:
In Essentials we can set the token length inside the Security - Providers for ArcGIS. Setting a longer token length in Essentials helped alleviate this issue. Ideally we would like to do this in web.
-
This one is worth following up as a support ticket. I tried orphaning a couple of authenticated apps and they were all successful at auto-updating a token without any error to the end user.
0 -
Hi Andrew Adamson! Yes, as Cam mentioned it would help us if you were to submit a support ticket describing this issue. I see you've already submitted several previous tickets to us, please send us another one to vertigisstudio-support@vertigis.com and we'd be glad to dig into this.
0 -
We are having the same problem and error that Andrew is seeing. Is there a fix for this? To note, only our services that are referencing data to our enterprise geodatabase are seeing this issue. Hosted data on our Portal does not.
Thanks,
0 -
Greg Anspach
Do you have any layers in your web map that contain saved credentials on them from other (non-federated) arc servers? If you do, or are unsure, after the app loads, check your dev console -> network tab for multiple generate token requests:
My conclusion in our ticket was: Having layers in a map that have stored credentials on the portal item cause multiple generateToken requests during load, if there are multiple generateToken requests, after 30 minutes, the app refresh function gets confused on what token to refresh, and the app goes into a stale/silent failure state.
We were under a time crunch so I just moved those layers around to our federated arc server and all was fixed. Unsure if this has been fixed in recent Web releases.0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires