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
I just noticed the login page when configured with Single Sign On did not automatically refreshed, so if a user logged out or inactive in login page for a long time then try login, it show 419 Page Expired error, the current workaround was refreshing the page
Steps to Reproduce
bookstack configured to SSO mode
go to bookstack login page and let the page inactive for few hours
try to login
it show 419 Page Expired
Expected Behaviour
after click login it should redirected to SSO login page
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
v24.02.2
The text was updated successfully, but these errors were encountered:
@ssddanbrown Can you clarify how CSRF tokens are reissued on session timeout, creation & end?
For example—say there are two tabs of bookstack open at the login page. A user can use one page to log into the app, do their thing and then close that tab. Come back in a few minutes to the previously open login tab, attempt a login and they'll receive a 419. Is there any keep-alive support for bookstack-issued CSRF tokens?
Describe the Bug
I just noticed the login page when configured with Single Sign On did not automatically refreshed, so if a user logged out or inactive in login page for a long time then try login, it show 419 Page Expired error, the current workaround was refreshing the page
Steps to Reproduce
Expected Behaviour
after click login it should redirected to SSO login page
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
v24.02.2
The text was updated successfully, but these errors were encountered: