How is the new signature algorithm different from the existing one for inbound API requests?
• The string to sign is formed in a different way. • HMAC-SHA256 can be used when the request is signed (we prefer HMAC-SHA256, but we still support HMAC-SHA1). • The SignatureVersion request parameter should be set to 2. • The SignatureMethod request parameter should be set to either HmacSHA256 or HmacSHA1 to indicate which signing method you want. • How is the new signature algorithm different from the existing one for outbound notifications (CBUI\Amazon Simple Pay return URLs and IPNs)? If you’re familiar with validating signature using version 1, these are the main differences with validating signature using version 2: • The string to sign is formed in a different way. • The signature computed is based on asymmetric keys (PKI and RSA-SHA1 encryption) instead of symmetric (using the developer’s AWS Access Key ID and AWS Secret Key). • Signature validation is simpler do to a VerifySignature API that can validate the signature returned in IPNs and Return URLs.
Related Questions
- Will the existing NBX 1102 Business Phones (10MB) ever support different languages? Is it because the smaller LCD does not support foreign characters?
- How is the new signature algorithm different from the existing one for outbound notifications (CBUIAmazon Simple Pay return URLs and IPNs)?
- What is different about forming the string to sign for signature version 2 (inbound and outbound)?
