I have a token that I pass to a resource header to create some 3dTiles. However, the token expires and requires a new token every so often. I used retryCallback to essentially get a new token based on the Cesium.Resource documentation. It somewhat works, but there also seem to be lingering requests using the old expired token, almost in parallel. Is there some sort of clean up or handling that I need to perform after the retryCallback to refresh token?
I did some more digging and noticed a similar behavior with WmtsProviders. For example, I created some view models using WmtsProviders and Resource that contains there token in the headers.
This works but noticed that the original request (with old token) continues to make the request, fails, retries, success. This causes the console to be spammed with 403s. I’ve also tried to set the selectedImagery to an updated viewModel, but that wipes the cached data on every token refresh.