AWS-SDK: RequestTimeTooSkewed in Chrome for Android
I'm developing an Angular 5/Ionic 3 app. The user can view and upload files to s3 directly from the frontend through credentials got from backend. To upload from backend is not an option in our case. I'm usin AWS-SDK-2.224.1
The S3 funcionaties of this application includes putObject, listObjects and deleteObject. It works correctly in the desktop and, at principle, at mobile phones. I've tested it on Chrome and Android.
The problem begins when the time of Android is wrong. In this case S3 funcionalities stays not avaiable and I get an error which says:
RequestTimeTooSkewed: The difference between the request time and the current time is too large.
We cannot control if the time in user's device is correct. For example, here in Brazil we have DST. Recently we've got problems involving Android automatic time changing in DST and now my Android don't changes the automatically. So I need to set it manually. But when I do it S3 fails.
How could I use S3 in the bowser whithout even with system time being wrong?


add a comment |
I'm developing an Angular 5/Ionic 3 app. The user can view and upload files to s3 directly from the frontend through credentials got from backend. To upload from backend is not an option in our case. I'm usin AWS-SDK-2.224.1
The S3 funcionaties of this application includes putObject, listObjects and deleteObject. It works correctly in the desktop and, at principle, at mobile phones. I've tested it on Chrome and Android.
The problem begins when the time of Android is wrong. In this case S3 funcionalities stays not avaiable and I get an error which says:
RequestTimeTooSkewed: The difference between the request time and the current time is too large.
We cannot control if the time in user's device is correct. For example, here in Brazil we have DST. Recently we've got problems involving Android automatic time changing in DST and now my Android don't changes the automatically. So I need to set it manually. But when I do it S3 fails.
How could I use S3 in the bowser whithout even with system time being wrong?


S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18
add a comment |
I'm developing an Angular 5/Ionic 3 app. The user can view and upload files to s3 directly from the frontend through credentials got from backend. To upload from backend is not an option in our case. I'm usin AWS-SDK-2.224.1
The S3 funcionaties of this application includes putObject, listObjects and deleteObject. It works correctly in the desktop and, at principle, at mobile phones. I've tested it on Chrome and Android.
The problem begins when the time of Android is wrong. In this case S3 funcionalities stays not avaiable and I get an error which says:
RequestTimeTooSkewed: The difference between the request time and the current time is too large.
We cannot control if the time in user's device is correct. For example, here in Brazil we have DST. Recently we've got problems involving Android automatic time changing in DST and now my Android don't changes the automatically. So I need to set it manually. But when I do it S3 fails.
How could I use S3 in the bowser whithout even with system time being wrong?


I'm developing an Angular 5/Ionic 3 app. The user can view and upload files to s3 directly from the frontend through credentials got from backend. To upload from backend is not an option in our case. I'm usin AWS-SDK-2.224.1
The S3 funcionaties of this application includes putObject, listObjects and deleteObject. It works correctly in the desktop and, at principle, at mobile phones. I've tested it on Chrome and Android.
The problem begins when the time of Android is wrong. In this case S3 funcionalities stays not avaiable and I get an error which says:
RequestTimeTooSkewed: The difference between the request time and the current time is too large.
We cannot control if the time in user's device is correct. For example, here in Brazil we have DST. Recently we've got problems involving Android automatic time changing in DST and now my Android don't changes the automatically. So I need to set it manually. But when I do it S3 fails.
How could I use S3 in the bowser whithout even with system time being wrong?




asked Nov 20 '18 at 16:39
NatanaelNatanael
4291720
4291720
S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18
add a comment |
S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18
S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397573%2faws-sdk-requesttimetooskewed-in-chrome-for-android%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397573%2faws-sdk-requesttimetooskewed-in-chrome-for-android%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
S3 uses GMT, so in theory,Time Zone shouldn't matter. But in reality - you're correct. You cannot control the time in the user's device. If the system time (with respect to GMT) is wrong - then you won't be able to authenticate with S3. You need to find a different way to authenticate :(
– FoggyDay
Nov 20 '18 at 16:46
What about enabling the option to correct for clock skew?
– Michael - sqlbot
Nov 21 '18 at 2:18