Angular detect when user leaves application












0















I've had a look around but I cannot seem to find the answer. Due to the "security" team at my company, they have stated that a website we have recently built, when a user navigates away from the website, we need to destroy the session.



Currently it's using a JWT token stored in the local browsers session, so when the user closes the browser the token will be destroyed.



So I know I can hook into window.onbeforeunload but this would also happen if the user refreshes the page, I don't think that would be acceptable behaviour for a website (refresh the page and now you are logged out). And there is also the Reload Site? popup that appears.



Does anyone know a way to detect that the user is navigating away from the angular app opposed to just reloading the page?










share|improve this question























  • I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

    – trichetriche
    Nov 26 '18 at 8:21











  • @trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

    – Jamie Rees
    Nov 26 '18 at 8:23











  • @trichetriche if you open the page in another window or tab it will initialize a new session storage

    – JEY
    Nov 26 '18 at 8:34











  • @JEY so tab closure should erase the storage then, right ?

    – trichetriche
    Nov 26 '18 at 8:39











  • yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

    – JEY
    Nov 26 '18 at 8:41
















0















I've had a look around but I cannot seem to find the answer. Due to the "security" team at my company, they have stated that a website we have recently built, when a user navigates away from the website, we need to destroy the session.



Currently it's using a JWT token stored in the local browsers session, so when the user closes the browser the token will be destroyed.



So I know I can hook into window.onbeforeunload but this would also happen if the user refreshes the page, I don't think that would be acceptable behaviour for a website (refresh the page and now you are logged out). And there is also the Reload Site? popup that appears.



Does anyone know a way to detect that the user is navigating away from the angular app opposed to just reloading the page?










share|improve this question























  • I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

    – trichetriche
    Nov 26 '18 at 8:21











  • @trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

    – Jamie Rees
    Nov 26 '18 at 8:23











  • @trichetriche if you open the page in another window or tab it will initialize a new session storage

    – JEY
    Nov 26 '18 at 8:34











  • @JEY so tab closure should erase the storage then, right ?

    – trichetriche
    Nov 26 '18 at 8:39











  • yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

    – JEY
    Nov 26 '18 at 8:41














0












0








0








I've had a look around but I cannot seem to find the answer. Due to the "security" team at my company, they have stated that a website we have recently built, when a user navigates away from the website, we need to destroy the session.



Currently it's using a JWT token stored in the local browsers session, so when the user closes the browser the token will be destroyed.



So I know I can hook into window.onbeforeunload but this would also happen if the user refreshes the page, I don't think that would be acceptable behaviour for a website (refresh the page and now you are logged out). And there is also the Reload Site? popup that appears.



Does anyone know a way to detect that the user is navigating away from the angular app opposed to just reloading the page?










share|improve this question














I've had a look around but I cannot seem to find the answer. Due to the "security" team at my company, they have stated that a website we have recently built, when a user navigates away from the website, we need to destroy the session.



Currently it's using a JWT token stored in the local browsers session, so when the user closes the browser the token will be destroyed.



So I know I can hook into window.onbeforeunload but this would also happen if the user refreshes the page, I don't think that would be acceptable behaviour for a website (refresh the page and now you are logged out). And there is also the Reload Site? popup that appears.



Does anyone know a way to detect that the user is navigating away from the angular app opposed to just reloading the page?







javascript angular security






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 8:19









Jamie ReesJamie Rees

4,77712960




4,77712960













  • I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

    – trichetriche
    Nov 26 '18 at 8:21











  • @trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

    – Jamie Rees
    Nov 26 '18 at 8:23











  • @trichetriche if you open the page in another window or tab it will initialize a new session storage

    – JEY
    Nov 26 '18 at 8:34











  • @JEY so tab closure should erase the storage then, right ?

    – trichetriche
    Nov 26 '18 at 8:39











  • yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

    – JEY
    Nov 26 '18 at 8:41



















  • I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

    – trichetriche
    Nov 26 '18 at 8:21











  • @trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

    – Jamie Rees
    Nov 26 '18 at 8:23











  • @trichetriche if you open the page in another window or tab it will initialize a new session storage

    – JEY
    Nov 26 '18 at 8:34











  • @JEY so tab closure should erase the storage then, right ?

    – trichetriche
    Nov 26 '18 at 8:39











  • yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

    – JEY
    Nov 26 '18 at 8:41

















I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

– trichetriche
Nov 26 '18 at 8:21





I don't see how you could distinguish the refresh from an actual leaving, but you could test storing the token in the session storage, that gets deleted when the user closes its browser. I'm not sure about a tab being closed though. Finally, you could also refuse the token once 10 min without requests have passed (this would be done in the back-end)

– trichetriche
Nov 26 '18 at 8:21













@trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

– Jamie Rees
Nov 26 '18 at 8:23





@trichetriche This was my initial thought. I was hoping for a answer to this question but I already know that I'm not going to get it!

– Jamie Rees
Nov 26 '18 at 8:23













@trichetriche if you open the page in another window or tab it will initialize a new session storage

– JEY
Nov 26 '18 at 8:34





@trichetriche if you open the page in another window or tab it will initialize a new session storage

– JEY
Nov 26 '18 at 8:34













@JEY so tab closure should erase the storage then, right ?

– trichetriche
Nov 26 '18 at 8:39





@JEY so tab closure should erase the storage then, right ?

– trichetriche
Nov 26 '18 at 8:39













yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

– JEY
Nov 26 '18 at 8:41





yes it's just a limitation. It's strange for the user to be logout when opening a new tab.

– JEY
Nov 26 '18 at 8:41












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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53477056%2fangular-detect-when-user-leaves-application%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
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53477056%2fangular-detect-when-user-leaves-application%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen