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
{{ message }}
This repository was archived by the owner on Oct 30, 2023. It is now read-only.
Took me a while, but I've identified a bug in 'AuthenticationInterceptor'.
Maybe it was not needed yet, but when I was locally implementing support for sub-account APIs and some of the query string parameters were containing email address (with @ symbol) then the request was failing with 'msg': -1022:Signature for this request is not valid
The issue is that 'AuthenticationInterceptor' is creating the SHA256 signature from original query string, for example: email=foo@bar.com
But it needs to be calculating it from URL encoded query string, for example: email=foo%40bar.com
Took me a while, but I've identified a bug in 'AuthenticationInterceptor'.
Maybe it was not needed yet, but when I was locally implementing support for sub-account APIs and some of the query string parameters were containing email address (with @ symbol) then the request was failing with 'msg':
-1022:Signature for this request is not validThe issue is that 'AuthenticationInterceptor' is creating the SHA256 signature from original query string, for example:
email=foo@bar.comBut it needs to be calculating it from URL encoded query string, for example:
email=foo%40bar.comPull request with fix: #298