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
Whenever the state in the login callback url fragment includes an equal sign, it looses anything after the equal sign. The reason for that it that decodeUriComponent is called on the whole url fragment before parsing it, leading to encoded characters in state to make new query params instead of still belonging to hash.
Code snippet or sample project that reproduces the bug
constlock=newLock('clientId','domain',{auth: {responseType: 'token',params: {// example 1state: '/some/path/to/redirect?q=firstparam&p=secondparam',// example 2state: 'asd&q=firstparam&p=secondparam'}}});lock.on('authenticated',function(result){// will log /some/path/to/redirect?q= for example 1// will log asd for example 2console.log(result.state);});
Lock version: 10.12.3
Browser & OS: Any
The text was updated successfully, but these errors were encountered:
Whenever the state in the login callback url fragment includes an equal sign, it looses anything after the equal sign. The reason for that it that
decodeUriComponent
is called on the whole url fragment before parsing it, leading to encoded characters in state to make new query params instead of still belonging to hash.The text was updated successfully, but these errors were encountered: