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
If you leave a browser tab logged into Bookstack via OIDC and then close the browser and return later after the session has expired - say the next day - when the page loads it will display the login page, but following the login link will result in a 419 - Page Expired error.
Manually refreshing the login page before clicking the login button works as expected.
Steps to Reproduce
Login to Bookstack via OIDC in a browser tab
Close browser
Reopen browser after login session has expired
Navigate to Bookstack tab
Click on OIDC Login button
See 419 error
Expected Behaviour
Login button should work even if the page itself is stale, or at least fail in a more recoverable way than a full-page 419 error.
Screenshots or Additional Context
No response
Browser Details
Firefox 126.0.1 (64-bit) on Windows 10
Exact BookStack Version
v24.05.1
The text was updated successfully, but these errors were encountered:
Describe the Bug
Seems to be a recurrance of #4600
If you leave a browser tab logged into Bookstack via OIDC and then close the browser and return later after the session has expired - say the next day - when the page loads it will display the login page, but following the login link will result in a 419 - Page Expired error.
Manually refreshing the login page before clicking the login button works as expected.
Steps to Reproduce
Login to Bookstack via OIDC in a browser tab
Close browser
Reopen browser after login session has expired
Navigate to Bookstack tab
Click on OIDC Login button
See 419 error
Expected Behaviour
Login button should work even if the page itself is stale, or at least fail in a more recoverable way than a full-page 419 error.
Screenshots or Additional Context
No response
Browser Details
Firefox 126.0.1 (64-bit) on Windows 10
Exact BookStack Version
v24.05.1
The text was updated successfully, but these errors were encountered: