Hi François, You might want to have a look at the code in Zinc-AWS (group AWS in ConfigurationOfZincHTTPComponents), in particular ZnAWSS3Client and ZnAWSS3RequestSignatureTool - it is using similar request signing but does HMAC-SHA1.
From a quick glance at the documentation, it seems you have to use Character lf (\r) else you'll get the wrong result. Have you tried signing the examples (canonical strings) in the documentation and comparing with their result ? If you really can't make it work, we can discuss further. Sven On 19 Jun 2014, at 10:05, François Stephany <[email protected]> wrote: > Hi there, > > I'm implementing a library to interact with Azure Storage. I'm already > blocked at the first step: generate the authentication header. > > The header generation is described there: > http://msdn.microsoft.com/en-us/library/azure/dd179428.aspx > > An SDK exists for Ruby: > https://github.com/Azure/azure-sdk-for-ruby > > I've taken the tests from the Ruby SDK to drive my implementation. I have a > mismatch that I can't solve with the authentication header. > > You can run the tests or execute the small scenario from the AZSharedKeyAuth > class comment to see where the problem is (i've created a temporary storage > account for testing, the account name and key are in the class comment). > > Apparently something goes wrong in the > signature= Base64(HMAC-SHA256(UTF8(StringToSign))). > > My StringToSign seems to be ok (cr vs lf vs crlf possibly put some mess). > > My code is there: > http://smalltalkhub.com/#!/~francois/AzureStorage > > Can someone have a look? If you're a company that can send invoices, I don't > mind to pay consulting fees if you can help... > >
