aws-amplify Auth.currentSession() not giving refreshed token after an hour
Which category is your question related to?
AWS amplify auto handling refresh token
What AWS Services are you utilizing?
aws-amplify
Provide additional details e.g. code snippets
axios.interceptors.request.use(function(config)
{ return Auth.currentSession() .then(session => { // User is logged in.
Set auth header on all requests
let accessToken = session.idToken.jwtToken;
axios.defaults.headers.common["Authorization"] = accessToken;
return Promise.resolve(config); })
.catch(() => {
// No logged-in user: don't set auth header
return Promise.resolve(config);
});
});
This is the interceptor request I'm using for now to get latest valid token irrespective of the total time, since user is logged-in as #446 and aws-amplify documentation tells that it is automatically refreshing token internally and Auth.currentSession() gives you the latest valid jwtToken every time.
But what I experience is: I login: Auth.currentSession() keeps giving me the jwtToken that was received when logged_in. After an hour, the token was expired and Auth.currentSession() was still giving this previous expired token which caused my server to send me 401. How do I handle it? How do I keep getting latest valid refreshed jwtToken? Am I using it wrong, or is it a bug?
javascript aws-amplify
edited Nov 21 '18 at 18:23
halfer
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
add a comment |
Which category is your question related to?
AWS amplify auto handling refresh token
What AWS Services are you utilizing?
aws-amplify
Provide additional details e.g. code snippets
axios.interceptors.request.use(function(config)
{ return Auth.currentSession() .then(session => { // User is logged in.
Set auth header on all requests
let accessToken = session.idToken.jwtToken;
axios.defaults.headers.common["Authorization"] = accessToken;
return Promise.resolve(config); })
.catch(() => {
// No logged-in user: don't set auth header
return Promise.resolve(config);
});
});
This is the interceptor request I'm using for now to get latest valid token irrespective of the total time, since user is logged-in as #446 and aws-amplify documentation tells that it is automatically refreshing token internally and Auth.currentSession() gives you the latest valid jwtToken every time.
But what I experience is: I login: Auth.currentSession() keeps giving me the jwtToken that was received when logged_in. After an hour, the token was expired and Auth.currentSession() was still giving this previous expired token which caused my server to send me 401. How do I handle it? How do I keep getting latest valid refreshed jwtToken? Am I using it wrong, or is it a bug?
javascript aws-amplify
edited Nov 21 '18 at 18:23
halfer
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26
add a comment |
Which category is your question related to?
AWS amplify auto handling refresh token
What AWS Services are you utilizing?
aws-amplify
Provide additional details e.g. code snippets
axios.interceptors.request.use(function(config)
{ return Auth.currentSession() .then(session => { // User is logged in.
Set auth header on all requests
let accessToken = session.idToken.jwtToken;
axios.defaults.headers.common["Authorization"] = accessToken;
return Promise.resolve(config); })
.catch(() => {
// No logged-in user: don't set auth header
return Promise.resolve(config);
});
});
This is the interceptor request I'm using for now to get latest valid token irrespective of the total time, since user is logged-in as #446 and aws-amplify documentation tells that it is automatically refreshing token internally and Auth.currentSession() gives you the latest valid jwtToken every time.
But what I experience is: I login: Auth.currentSession() keeps giving me the jwtToken that was received when logged_in. After an hour, the token was expired and Auth.currentSession() was still giving this previous expired token which caused my server to send me 401. How do I handle it? How do I keep getting latest valid refreshed jwtToken? Am I using it wrong, or is it a bug?
javascript aws-amplify
edited Nov 21 '18 at 18:23
halfer
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
Which category is your question related to?
AWS amplify auto handling refresh token
What AWS Services are you utilizing?
aws-amplify
Provide additional details e.g. code snippets
axios.interceptors.request.use(function(config)
{ return Auth.currentSession() .then(session => { // User is logged in.
Set auth header on all requests
let accessToken = session.idToken.jwtToken;
axios.defaults.headers.common["Authorization"] = accessToken;
return Promise.resolve(config); })
.catch(() => {
// No logged-in user: don't set auth header
return Promise.resolve(config);
});
});
This is the interceptor request I'm using for now to get latest valid token irrespective of the total time, since user is logged-in as #446 and aws-amplify documentation tells that it is automatically refreshing token internally and Auth.currentSession() gives you the latest valid jwtToken every time.
But what I experience is: I login: Auth.currentSession() keeps giving me the jwtToken that was received when logged_in. After an hour, the token was expired and Auth.currentSession() was still giving this previous expired token which caused my server to send me 401. How do I handle it? How do I keep getting latest valid refreshed jwtToken? Am I using it wrong, or is it a bug?
javascript aws-amplify
javascript aws-amplify
edited Nov 21 '18 at 18:23
halfer
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
edited Nov 21 '18 at 18:23
halfer
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
edited Nov 21 '18 at 18:23
halfer
14.7k759116
edited Nov 21 '18 at 18:23
halfer
14.7k759116
edited Nov 21 '18 at 18:23
halfer
14.7k759116
14.7k759116
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
asked Nov 21 '18 at 6:19
ghazanfar malikghazanfar malik
31
31
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26
add a comment |
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26
add a comment |
0
active
oldest
votes
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%2f53406285%2faws-amplify-auth-currentsession-not-giving-refreshed-token-after-an-hour%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%2f53406285%2faws-amplify-auth-currentsession-not-giving-refreshed-token-after-an-hour%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
Please read Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers? - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions.
– halfer
Nov 21 '18 at 18:24
Any answers from AWS to this issue? I'm facing the same problem in my application
– dev1702
Jan 18 at 9:26