-
Notifications
You must be signed in to change notification settings - Fork 71
Sign2 succeeds, but Sign4 403 forbidden #2
Comments
Does it work if you just use the |
Hi Matt, No, that doesn't work either. However, I did figure out the issue. This works: This fails: Amazon requires the parameter keys in canonical order (i.e. alphabetical). Thanks, On Sat, Jan 25, 2014 at 10:18 AM, Matt notifications@github.com wrote:
|
Thanks, and yes, the canonical ordering does seem right. Hm, I wonder how the tests are passing, then. It's been a while since I've looked at this code, but when I get a chance, I'll dive in and try to figure out why the request's parameters aren't being ordered properly. |
@mikev I'm able to reproduce this -- looks like the tests just got lucky. I'll work on a fix. Update: Well, that was quite easy. Silly me. Thanks for the report! |
Cool. Thanks! On Sun, Jan 26, 2014 at 12:24 PM, Matt notifications@github.com wrote:
|
Hi Matt, Any chance to add Sign3 (Signature version 3)? It is used by AWS Route53 Best, On Sun, Jan 26, 2014 at 4:47 PM, Michael Vierling mvierling@gmail.comwrote:
|
Oh. Version 3?? I've never heard of it. Googling Route53 authentication, though, I see this documentation. I'm not sure that it's called Version 3, but it definitely appears to be its own authentication scheme. I can look into adding support for it. For a quicker turnaround, you're welcome to take a stab at it. A good starting point would be s3.go and s3_test.go, which has a similar procedure. I hope to get to this soon, as I agree, it's an important addition. |
OK, draft working code enclosed. I tested against route53 and the Cheers, On Thu, Jan 30, 2014 at 6:07 AM, Matt notifications@github.com wrote:
|
@mikev Hm, if you attached something, it didn't come through. What about a pull request? Or you could email me directly with the attachment. Thanks for the link, by the way -- I'll take a look soon. Update: Got your email. Cheers. I'm going to put this into a new issue; I'm starting on this on Saturday! |
The following test for an SQS resource, succeeds with Sign2, but fails when Sign4 is substituted, otherwise code is identical. Error code returned is 403 forbidden.
The text was updated successfully, but these errors were encountered: