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
This issue occurs when btoa appends an '=' to the stringfy data object for base64 encoding. The state data then contains a %3D encoded character after it round trips from IDP login which causes TransactionManager to attempt to locate the transaction as 'ASDF%3D' instead of 'ASDF='
I've updated my own code to strip the padding character. Not sure this should be fixed in auth0 as = should not be passed in the first place but I am seeing btoa include it.
This issue occurs when btoa appends an '=' to the stringfy data object for base64 encoding. The state data then contains a %3D encoded character after it round trips from IDP login which causes TransactionManager to attempt to locate the transaction as 'ASDF%3D' instead of 'ASDF='
Issue can be resolved by adding the following on line 51 of transaction-manager.js
Occurs in chrome v56
The text was updated successfully, but these errors were encountered: