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
Which packages do you think might be impacted by the bug ?
solid-client-authn-browser
solid-client-authn-core
Bug description
In some conditions which are still unclear, we get issue with storing/retrieving the sessionId of the current user from the default storage (which is the localStorage in that case).
Probably linked to that one we described before: #423 (comment)
When logging-in back, he is sometimes stuck on the ?code=[code]&state=[state] step of the authentication workflow
Expected result
User should come back whenever he wishes to the app, either having triggered the logout when he closed before or not, and the new login attempt should work as expected.
Actual result
In some conditions which are still unclear, the new login attempt is triggered but stays stuck at the ?code=[code]&state=[state] step with the message in the console being:
oidc.js:422 Uncaught (in promise) Error: Field [sessionId] for user [0e5bb174de6f43318335a18d481e4d36] is not stored
at StorageUtilityBrowser.getForUser (oidc.js:3994)
at async AuthCodeRedirectHandler.handle (oidc.js:14154)
at async ClientAuthentication.handleIncomingRedirect (oidc.js:13683)
at async Session.handleIncomingRedirect (oidc.js:14566)
The only way to make it work from here is to trigger an additional reload of our app, which triggers the login again, skipping the login/password screen as the user is already authenticated, so just sending him to the authorization screen, then back to the app with a new code which actually passes.
We are using the defaultStorage for those information which is the localStorage as far as I get it.
Search terms you've used
Field [sessionId] for user is not stored
Impacted package
Which packages do you think might be impacted by the bug ?
Bug description
In some conditions which are still unclear, we get issue with storing/retrieving the sessionId of the current user from the default storage (which is the localStorage in that case).
Probably linked to that one we described before: #423 (comment)
To Reproduce
?code=[code]&state=[state]
step of the authentication workflowExpected result
User should come back whenever he wishes to the app, either having triggered the logout when he closed before or not, and the new login attempt should work as expected.
Actual result
In some conditions which are still unclear, the new login attempt is triggered but stays stuck at the
?code=[code]&state=[state]
step with the message in the console being:The only way to make it work from here is to trigger an additional reload of our app, which triggers the login again, skipping the login/password screen as the user is already authenticated, so just sending him to the authorization screen, then back to the app with a new code which actually passes.
We are using the defaultStorage for those information which is the localStorage as far as I get it.
Environment
Available if needed for additional info or debugging session or context understanding.
The text was updated successfully, but these errors were encountered: