Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClockSkewInterceptor not used when calculating the signature #1033

Open
rcoh opened this issue Jan 4, 2024 Discussed in #1029 · 0 comments
Open

ClockSkewInterceptor not used when calculating the signature #1033

rcoh opened this issue Jan 4, 2024 Discussed in #1029 · 0 comments
Labels
bug This issue is a bug. p2 This is a standard priority issue

Comments

@rcoh
Copy link
Contributor

rcoh commented Jan 4, 2024

Discussed in #1029

Originally posted by moranbw January 2, 2024
It looks like some AWS SDKs have flags for a "clock skew", while some "automatically" apply this, like the v3 Javascript API.

I have a feeling that the Rust SDK does not? I was having issues with a Windows user authenticating, getting persistent SignatureDoesNotMatch errors. As a random guess, I asked if their clock was in sync. They had manually set it. I had them turn the time and timezone on to automatically set, and voila -- authentication worked immediately.

Is there any way I can programmatically account for this in my application?

@rcoh rcoh added the bug This issue is a bug. label Jan 4, 2024
@jmklix jmklix added the p2 This is a standard priority issue label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

2 participants