Closed s3645t14n closed 3 years ago
brockallen
commented
3 years ago and silent_renew.html running every 3 seconds.
Why so frequent? Access tokens that short seem like a poor choice.
Usually everything works fine, but when user loads some maps, network gets flooded with .png tiles requests.
Likely because the browser only allows so many outbound HTTP calls at a time.
s3645t14n
commented
3 years ago Why so frequent? Access tokens that short seem like a poor choice.
That was system developer's choice, I'm not really sure why, I'm a very inexpirienced JS-developer myself. I thought that it checks (every 3 sec) if token is expired and renews it if it is, but maybe I'm wrong and it doesn't work like this.
Likely because the browser only allows so many outbound HTTP calls at a time.
Is it possible that due to HTTP call limit iframe gets timeout while pending when there's too many of those png requests? What exactly "Frame window timeout" means in terms of this oidc implementation?
brockallen
commented
3 years ago Is it possible that due to HTTP call limit iframe gets timeout while pending when there's too many of those png requests? What exactly "Frame window timeout" means in terms of this oidc implementation?
Token renewal in the iframe and it's based on the user's SSO cookie at the IdP. The iframe might timeout because it's showing an error page, or it's just too slow because the browser's not making the HTTP request due to the other outbound calls. I don't know which one it is, tho, in your case.
brockallen
commented
3 years ago If it is a timeout because an error page is being displayed, then check the logs in your IdP to see if that helps identify the issue. Report back, please, if you think/find there's a bug in this library.
Hello,
we have a geo-informational system running and we got an issue with user sessions unexpectedly ending when the user is actively working with maps.
I'm a system administrator so I dont have direct access to source code, but in the network logs I see that the system is apparently using implicit flow with token life around 4 min and silent_renew.html running every 3 seconds.
Usually everything works fine, but when user loads some maps, network gets flooded with .png tiles requests. If token happens to expire in the same time there is almost 100% probability that it fails to renew and session will close (it actually can close even if token isn't yet expired, just because of loading excessive amount of maps and flooding network with requests). In console log I see this:
It looks like corresponding authorize request is gets through but to no avail:
What I did:
Now I don't expect to learn the reason for this behavior right away, but would be very grateful if someone could advice me where to look. For now I'm not even sure what does "Frame window timeout" actually means. Is it what happening when iFrame gets incorrect answer with its authorize request?
Sorry for my English, thanks for any help.