Application Times-out and requests user's credentials
We have an ExB application running on top for ArcGIS Enterprise 10.9.0. AGS enterprise is using Integrated Windows authentication to authenticate users and Single Sign On is enabled (users never enter their credentials).
The application works fine, however after 30 minutes or so, they authentication seems to "timeout" and the user gets a message saying "Please sign in to access the item" (see below). You can't put your credentials here since the system is using IWA, so the only way to continue using the app is to reload the full app and start over again.
I thought it might be due to inactivity, but it's not. I even added a component that will make a query to Portal every minute to see if this will keep it alive, but didn't work.
Any thoughts on this?
Thanks!
Alejandro
Oh boy, I am not sure this will be a guarantee fix for everyone, but I can go through my journey that may be of some help, keeping in mind that “your mileage may vary”.
Environment setup:
- ArcGIS Enterprise 11.2
- ExB Dev edition 1.13 -> Deployed on Azure Static Web Apps
- Azure AD for SSO
- Checking the portal expiry from the ArcGIS Portal: https://enterprise.arcgis.com/en/portal/latest/administer/windows/specify-the-default-token-expirati.... Ours is set as -1 which means it’s the max of two weeks:
- Check the ArcGIS server tokens here: https://enterprise.arcgis.com/en/server/latest/administer/windows/editing-token-settings-in-manager..... There are short-live and Long-lived tokens, just be careful to not go too long of a lifespan but it could be causing timeouts if an expiring date is not being provided from the ExB/Javascript code.
- We currently have our CORS policy empty in arcigs portal settings to accept all domains (as in its just blank): https://enterprise.arcgis.com/en/portal/latest/administer/windows/restrict-cross-domain-requests-to-...
- I was ignoring the “cannot register the service worker” warning that was in the developer console when first accessing the app, but I resolved that due to a trailing slash (“/”) problem in URL and how the app was deployed in Azure Static Web App. So, I recommend making sure you see the “register a service worker”:
- This led to my to my additional problem of when ExB does a token refresh I noticed it was erroring out from looking at the network requests in the developer tools (I’m using Chrome). Having that trailing slash caused an error in the token refresh. Might be worth looking into the network call if its erroring out to try and narrow it down from there.
- Other things, I upgraded to use the recommended Node.js and React version to 18 when using the dev edition builder.
- Upgrade to ExB 1.14 and hope its all fixed 😊. I am personally going to wait for our enterprise to get upgraded to 11.3 before I move into that version because I am starting to get the feel that going too far ahead with the ExB version compared to Enterprise seems to be cause more issues now.
Looking back, I would have just spent more time with a pure ArcGIS JavaScript SDK solution instead of trying to leverage ExB...
