Best way to redirect user after login using ASP.NET Identity and Knockout
I have implemented ASP.NET Identity and OWIN in my site. To make the authentication, I am using Knockout calls.
This is the Javascript method that does the actual login:
self.login = function () {
self.result('');
self.errors.removeAll();
var loginData = {
grant_type: 'password',
username: self.loginEmail(),
password: self.loginPassword()
};
if (loginData.username && loginData.password && loginData.username != '' && loginData.password != '') {
$.ajax({
type: 'POST',
url: '/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
}).fail(showError);
}
}
It works... when authentication failed, it shows an error, but the question is regarding successful login. What is the best practice to do the redirect to a secured page? I think that doing location.href = '' is an old way. Is there a modern way to do this? How to manage if there is a return url querystring parameter?
Thanks
Jaime
authentication asp.net-identity owin
add a comment |
I have implemented ASP.NET Identity and OWIN in my site. To make the authentication, I am using Knockout calls.
This is the Javascript method that does the actual login:
self.login = function () {
self.result('');
self.errors.removeAll();
var loginData = {
grant_type: 'password',
username: self.loginEmail(),
password: self.loginPassword()
};
if (loginData.username && loginData.password && loginData.username != '' && loginData.password != '') {
$.ajax({
type: 'POST',
url: '/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
}).fail(showError);
}
}
It works... when authentication failed, it shows an error, but the question is regarding successful login. What is the best practice to do the redirect to a secured page? I think that doing location.href = '' is an old way. Is there a modern way to do this? How to manage if there is a return url querystring parameter?
Thanks
Jaime
authentication asp.net-identity owin
add a comment |
I have implemented ASP.NET Identity and OWIN in my site. To make the authentication, I am using Knockout calls.
This is the Javascript method that does the actual login:
self.login = function () {
self.result('');
self.errors.removeAll();
var loginData = {
grant_type: 'password',
username: self.loginEmail(),
password: self.loginPassword()
};
if (loginData.username && loginData.password && loginData.username != '' && loginData.password != '') {
$.ajax({
type: 'POST',
url: '/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
}).fail(showError);
}
}
It works... when authentication failed, it shows an error, but the question is regarding successful login. What is the best practice to do the redirect to a secured page? I think that doing location.href = '' is an old way. Is there a modern way to do this? How to manage if there is a return url querystring parameter?
Thanks
Jaime
authentication asp.net-identity owin
I have implemented ASP.NET Identity and OWIN in my site. To make the authentication, I am using Knockout calls.
This is the Javascript method that does the actual login:
self.login = function () {
self.result('');
self.errors.removeAll();
var loginData = {
grant_type: 'password',
username: self.loginEmail(),
password: self.loginPassword()
};
if (loginData.username && loginData.password && loginData.username != '' && loginData.password != '') {
$.ajax({
type: 'POST',
url: '/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
}).fail(showError);
}
}
It works... when authentication failed, it shows an error, but the question is regarding successful login. What is the best practice to do the redirect to a secured page? I think that doing location.href = '' is an old way. Is there a modern way to do this? How to manage if there is a return url querystring parameter?
Thanks
Jaime
authentication asp.net-identity owin
authentication asp.net-identity owin
edited Nov 20 '18 at 21:51
R. Richards
14.5k93742
14.5k93742
asked Nov 20 '18 at 20:49
jstuardojstuardo
1,00352962
1,00352962
add a comment |
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%2f53401289%2fbest-way-to-redirect-user-after-login-using-asp-net-identity-and-knockout%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%2f53401289%2fbest-way-to-redirect-user-after-login-using-asp-net-identity-and-knockout%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