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
If you have an Url hash with encoded special characters (%,&,?, ...), the URI malformed error will be thrown when calling OAuthService:loadDiscoveryDocumentAndLogin without providing a custom hash fragment.
After some code analysis I noticed that this was due to double decoding of the hash fragment:
getCodePartsFromUrl calls this.urlHelper.getHashFragmentParams(); if no queryString (no customHashFragment or window.location.search)
getHashFragmentParams first decodes window.location.hash and then executes this.parseQueryString(hash) with that decoded hash,
parseQueryString decodes the url hash again (see value = decodeURIComponent(escapedValue));, which results in ERROR URIError: URI malformed
The text was updated successfully, but these errors were encountered:
If you have an Url hash with encoded special characters (%,&,?, ...), the URI malformed error will be thrown when calling
OAuthService:loadDiscoveryDocumentAndLogin
without providing a custom hash fragment.After some code analysis I noticed that this was due to double decoding of the hash fragment:
this.urlHelper.getHashFragmentParams()
; if no queryString (no customHashFragment or window.location.search)window.location.hash
and then executesthis.parseQueryString(hash)
with that decoded hash,value = decodeURIComponent(escapedValue)
);, which results in ERROR URIError: URI malformedThe text was updated successfully, but these errors were encountered: