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
When an OIDC sign-in attempt fails and the user is shown a Grist error page with a Sign in again button:
Then, even when the new attempt succeeds, the user is still shown the error page (despite now being signed in, as shown in the top right corner).
Steps to reproduce
Begin an OIDC login process from an unauthenticated Grist tab
Before completing the login process, clear the Grist cookies from the browser (this can be done from a separate tab in the same browser browsing the same Grist instance) — note that this is one way of reliably producing an OIDC callback error, but any other error sent by the OIDC provider would result in the behavior described below
Complete the OIDC login process: Grist shows an error (as expected) and offers to try signing in again
When the user clicks "sign in again", assuming there is no further OIDC error, the login process completes, but the user is still shown Grist's OIDC error page instead of a workspace home page.
grist-oidc-stuck-on-sign-in.mp4
Describe the expected behavior
When retrying an OIDC sign-in succeeds, the user should end up on the same page they would have if the initial attempt had succeeded.
Describe the current behavior
When an OIDC sign-in attempt fails and the user is shown a Grist error page with a Sign in again button:
Then, even when the new attempt succeeds, the user is still shown the error page (despite now being signed in, as shown in the top right corner).
Steps to reproduce
grist-oidc-stuck-on-sign-in.mp4
Describe the expected behavior
When retrying an OIDC sign-in succeeds, the user should end up on the same page they would have if the initial attempt had succeeded.
Where have you encountered this bug?
Instance information (when self-hosting only)
Grist instance:
main
(commit d06def9)http://grist-home.127.0.0.1.nip.io:8484/
Server log:
The text was updated successfully, but these errors were encountered: