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
Right now if the hash contains an = it is assumed to "belong" to the remotestorage.js oauth flow and is removed in its entirely. This is very annoying for websites that want to use the hash themselves. Instead the hash should only be removed if there is strong evidence to indicate that we are doing the remotestorage.js oauth flow (for example rsDiscovery or access_token and state are set). Ideally even stronger verification could be done such as embedding a random value that is unlikey to be used by the embedding application.
Right now if the hash contains an
=
it is assumed to "belong" to the remotestorage.js oauth flow and is removed in its entirely. This is very annoying for websites that want to use the hash themselves. Instead the hash should only be removed if there is strong evidence to indicate that we are doing the remotestorage.js oauth flow (for examplersDiscovery
oraccess_token
andstate
are set). Ideally even stronger verification could be done such as embedding a random value that is unlikey to be used by the embedding application.remotestorage.js/src/authorize.js
Lines 215 to 220 in 61cbbb2
The text was updated successfully, but these errors were encountered: