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
Since the oauth api accepts now the nonce param (due to the open id connect changes), we might think about moving the security token to the nonce instead of the state. Also helping us to use the state for other stuff
It sounds like we might need both - is this right?:
If you're using login (/sessions), we're going to get an identity token back, and we can use the embedded nonce attribute as a safe alternative to the state parameter
If you're using connect (/connections), we won't get an identity token back, and will therefore need to use state
Since the oauth api accepts now the nonce param (due to the open id connect changes), we might think about moving the security token to the nonce instead of the state. Also helping us to use the state for other stuff
see also https://stackoverflow.com/questions/46844285/difference-between-oauth-2-0-state-and-openid-nonce-parameter-why-state-cou
The text was updated successfully, but these errors were encountered: