Is there any way to check authorization before accessing indexedDB or localStorage?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I would like to access either indexedDB or localStorage while the user is logged in to the website, and deny access to that info while the user is logged out. Is there any way to do so?
javascript web browser local-storage indexeddb
add a comment |
I would like to access either indexedDB or localStorage while the user is logged in to the website, and deny access to that info while the user is logged out. Is there any way to do so?
javascript web browser local-storage indexeddb
add a comment |
I would like to access either indexedDB or localStorage while the user is logged in to the website, and deny access to that info while the user is logged out. Is there any way to do so?
javascript web browser local-storage indexeddb
I would like to access either indexedDB or localStorage while the user is logged in to the website, and deny access to that info while the user is logged out. Is there any way to do so?
javascript web browser local-storage indexeddb
javascript web browser local-storage indexeddb
edited Jan 9 at 4:57


Josh
11.7k63855
11.7k63855
asked Jan 3 at 8:41
richard nelsonrichard nelson
1186
1186
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If I imagine following use-case: restrict non-authorized user from accessing sensitive data, which was previously stored by authorized user on the same device, I may consider storing encrypted values that can be deciphered upon successful login with the key from the server. For sure, it will not guarantee data security, but it will definitely ruin app performance that is expected to get boosted by IndexedDB or localStorage.
add a comment |
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%2f54018848%2fis-there-any-way-to-check-authorization-before-accessing-indexeddb-or-localstora%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If I imagine following use-case: restrict non-authorized user from accessing sensitive data, which was previously stored by authorized user on the same device, I may consider storing encrypted values that can be deciphered upon successful login with the key from the server. For sure, it will not guarantee data security, but it will definitely ruin app performance that is expected to get boosted by IndexedDB or localStorage.
add a comment |
If I imagine following use-case: restrict non-authorized user from accessing sensitive data, which was previously stored by authorized user on the same device, I may consider storing encrypted values that can be deciphered upon successful login with the key from the server. For sure, it will not guarantee data security, but it will definitely ruin app performance that is expected to get boosted by IndexedDB or localStorage.
add a comment |
If I imagine following use-case: restrict non-authorized user from accessing sensitive data, which was previously stored by authorized user on the same device, I may consider storing encrypted values that can be deciphered upon successful login with the key from the server. For sure, it will not guarantee data security, but it will definitely ruin app performance that is expected to get boosted by IndexedDB or localStorage.
If I imagine following use-case: restrict non-authorized user from accessing sensitive data, which was previously stored by authorized user on the same device, I may consider storing encrypted values that can be deciphered upon successful login with the key from the server. For sure, it will not guarantee data security, but it will definitely ruin app performance that is expected to get boosted by IndexedDB or localStorage.
answered Jan 3 at 16:04
Yevgen GorbunkovYevgen Gorbunkov
1,54231634
1,54231634
add a comment |
add a comment |
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%2f54018848%2fis-there-any-way-to-check-authorization-before-accessing-indexeddb-or-localstora%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