however accessing the blob gives the following error:
<Error><Code>AuthenticationFailed</Code> <Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Time:2011-12-15T01:08:39.6475705Z </Message> <AuthenticationErrorDetail>Signature did not match. String to sign used was r2011-12-15T02:08:31Z/REMOVEDADDRESS
It looks like my DateTime.UtcNow gives a different time to what azure is using.
Hi, looks like you haven't specified start time. You need to specify SharedAccessStartTime. Note due to clock drift, usually you want to set start time to 1 minute before the current time instead of the current time, so SAS will work immediately.Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact
firstname.lastname@example.org. Microsoft One Code Framework
You do not have to provide a start time as it is optional.
Just curious: does it fail even if you try after some time or does that succeed? Have you verified that the key is correct? If it does not succeed after sometime and your key is correct, we may need your account name and request id. If you can send it to
jharidas at microsoft, that will be great.
I've tried what MingXu-MSFT suggested and set the start time as well as the expiration time.
Now it's starting to look really weird because my time looks like it falls within the valid access window.
<Error><Code>AuthenticationFailed</Code><Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
</Message><AuthenticationErrorDetail>Signature did not match. String to sign used was r
Also Jai, I have sent you an email with my service subscription details. Have you got it or should I try to email again?
Edited byKym McGainWednesday, December 21, 2011 9:54 PMRemoved private information