Glad with this thread dilettante, especially:
I hope this helps.

Going through the AWS SimpleDB documentation for REST Authentication I find the docs are good but not great. They leave out small tidbits and swing between specific and vague on important things like character encoding, what precisely they mean by "newline" and other small things. HS256 itself took some work, but figuring out the AWS "canonicalization" process is a small nightmare. They outline the steps but leaving you hanging here and there on specifics.

They even give an example but don't show what the final Signature should be, making verification of my example here difficult.

In any case, the example attached here is way stripped down but with copious comments. In those comments I have made notes about a few points you may need to get clarification on. Try the AWS developer support forums for answers.


Keep in mind that different Amazon Services have different requirements. Grab all of the docs they offer (old and new) for the Service you need to use.
It's very nice,thank you.

Because general principle of OAuth is same (using HMAC-SHA1 or RSA-SHA1), what if made ​​into OAuth Class (clsOAuth.cls) for generate a signature (it will be very useful), so with the signature generated by OAuth class (clsOAuth.cls) we can easily access:
  1. Amazon API
  2. Twitter API
  3. Google API
  4. Facebook API
  5. etc ... API with OAuth.

Because it's very hard to find in Google, OAuth Class created with VB6. I've tried to modify the code and make clsOAuth.cls but it always fails and displays the error message:

HTTP/1.1 401 Unauthorized or Invalid Signature and token.

Sorry for my english. Thank you.