You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: