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
The signature parameters segment of Signature-Input is specified to support the following parameters:
created
expires
nonce
alg
keyid
tag
In the code (signature-base-helper.generateBase()), it seems that the created field is automatically appended, and there's no support for the other fields.
...I can append whatever I want. However, signature-helper.generateSignature() will then re-generate the base string using signature-base-helper.generateBase(), overwriting whatever I added to it previously, and sign that instead. Therefore, whatever I append myself to Signature-Input (like keyid) will not be represented in the signature, and will fail verification on the receiving endpoint.
It's possible to pass keyid in a separate header, but that seems messy. Is there a way to pass this in the Signature-Input header?
The text was updated successfully, but these errors were encountered:
@TurboEncabulator9000 The x-ebay-signature-key header already contains the encrypted keyid. Could you please provide more information about your specific use case?
The signature parameters segment of
Signature-Input
is specified to support the following parameters:created
expires
nonce
alg
keyid
tag
In the code (
signature-base-helper.generateBase()
), it seems that thecreated
field is automatically appended, and there's no support for the other fields.If I try to wrap the library like this...
...I can append whatever I want. However,
signature-helper.generateSignature()
will then re-generate the base string usingsignature-base-helper.generateBase()
, overwriting whatever I added to it previously, and sign that instead. Therefore, whatever I append myself toSignature-Input
(likekeyid
) will not be represented in the signature, and will fail verification on the receiving endpoint.It's possible to pass
keyid
in a separate header, but that seems messy. Is there a way to pass this in theSignature-Input
header?The text was updated successfully, but these errors were encountered: