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
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Currently, we only save one value of nonce and state. This will not work in cases when user has multiple tabs open. Consider the scenario:
User opens the app in tab 1, clicks on login, gets redirected to AAD => this will set the session nonce
User open the app in tab 2, clicks on login, gets redirected to AAD => this will overwrite the nonce set int the step above
User logs in tab 1, the nonce validation will fail. This will return an error to the app that nonce did not match.
Also, we should delete the nonce only if it matches, otherwise not. We need to think about saving multiple nonces at a time.
Same applies for state.
The text was updated successfully, but these errors were encountered:
Handling multiple nonce/state pairs means we can't remove them from session automatically, so we'll need an expiration policy and cleanup process to remove old nonce/state pairs from the session.
Currently, we only save one value of nonce and state. This will not work in cases when user has multiple tabs open. Consider the scenario:
User opens the app in tab 1, clicks on login, gets redirected to AAD => this will set the session nonce
User open the app in tab 2, clicks on login, gets redirected to AAD => this will overwrite the nonce set int the step above
User logs in tab 1, the nonce validation will fail. This will return an error to the app that nonce did not match.
Also, we should delete the nonce only if it matches, otherwise not. We need to think about saving multiple nonces at a time.
Same applies for state.
The text was updated successfully, but these errors were encountered: