Amazon Simple Pay
Advanced User Guide (API Version 2010-08-28)
AWS Documentation » Amazon Simple Pay » Advanced Guide » Appendix: Moving your Application to Signature Version 2
Print this pageEmail this pageGo to the ForumsView the PDFShare this page on TwitterShare this page on FacebookBookmark this page on DeliciousSubmit this page to RedditSubmit this page to DiggDid this page help you?  Yes  No   Tell us about it...

Appendix: Moving your Application to Signature Version 2

Amazon deprecated Signature version 1 on November 3rd, 2009, and as of 10 February, 2011. You must migrate your applications that use signature version 1 to signature version 2. This section details how to migrate to signature version 2 for inbound requests and outbound responses.

Amazon provides code samples to assist you in migrating your signature version 1 code to signature version 2. The samples are packaged in five programming languages (C#, Java, Perl, PHP, and Ruby), they are available from the Amazon Web Services developer community, under the Amazon Flexible Payments Service category.

The following sections describe the high-level process for migrating your signature version 1 signing code.

For information on using Amazon Simple Pay sample code, see Appendix: Sample Code

Migrating Inbound Requests to Signature Version 2

If you are currently signing your buttons using a signature calculated using signature version 1, you need to make the following changes:

  • Modify the way you assemble your signature. For more information, see How to Generate a Signature and Differences Between Signing Versions.

  • Include the value 2 for the required SignatureVersion parameter in your button forms and FPS actions.

  • Determine your preferred signing algorithm (either the preferred HmacSHA256, or HmacSHA1), and set the SignatureMethod parameter to the corresponding value in your button forms and FPS actions.

  • Check that your encryption method supports your chosen algorithm, and rewrite it if necessary.

After you change your code, validate it in the Amazon FPS sandbox. You can check your signature code using the samples listed in this guide. For more information, see Appendix: Sample Code.

Migrating Outbound Notifications to Signature Version 2

If you are currently validating return URL and IPN notifications using signature version 1:

Adjust the way you build the signature to comply with signature version 2. For more information, see How to Generate a Signature and Differences Between Signing Versions.

[Important]Important

The original implementation of signature version 2 supported client-side signature validation using PKI. Client-side signature validation was deprecated on November 3rd, 2009, and as of 10 February, 2011 it is no longer supported. If you have been using client-side signature validation, you must switch to server-side validation using the FPS action VerifySignature.

Document Conventions
Terms of Use		Did this page help you?  Yes  No   Tell us about it...