You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the device is in sleep mode, the access token is not refreshed as it should be. This leads to an 401 error - for the user it looks like the page suddenly just started not responding. The workaround is to open a new tab with the same url - this is of course not apparent for users.
Is this a regression?
No.
To Reproduce
Steps to reproduce the behavior:
keep the device in sleep mode, when the refresh is scheduled. The you can observe the behaviour.
Expected behavior
the application should either refresh the token when the user comes back online, or should log the user out. You can take inspiration from here manfredsteyer/angular-oauth2-oidc#820.
Environment
Chrome 127.0.6533.89
Damap version 4.0.0
The text was updated successfully, but these errors were encountered:
Describe the bug
When the device is in sleep mode, the access token is not refreshed as it should be. This leads to an 401 error - for the user it looks like the page suddenly just started not responding. The workaround is to open a new tab with the same url - this is of course not apparent for users.
Is this a regression?
No.
To Reproduce
Steps to reproduce the behavior:
keep the device in sleep mode, when the refresh is scheduled. The you can observe the behaviour.
Expected behavior
the application should either refresh the token when the user comes back online, or should log the user out. You can take inspiration from here manfredsteyer/angular-oauth2-oidc#820.
Environment
The text was updated successfully, but these errors were encountered: