Using JSON Web Token to secure Web API communication
I'm trying to implement JWT mechanism to secure communication between the .NET MVC application and Web API application acting as a server for this and other apps that reside on the same Windows network.
All apps would have a Client Key in form of Guid by which the Web API app can get them authenticated. There is a lot of examples on how to implement a scenario when the end user is getting authenticated by entering credentials in the UI or by implementing an Authentication Server between the app and Web API.
I'm wondering if there is a way to allow users of the app to receive a response seamlessly without entering credentials or being redirected to Authentication Server?
Not sure but I guess I'm wanting to have a class that generates JSON Web Tokens and is used in data annotation on server's action methods like [ValidateAntiForgeryToken]
is used to establish secure communication between browser and server.
Any ideas will be much appreciated.
c# jwt
add a comment |
I'm trying to implement JWT mechanism to secure communication between the .NET MVC application and Web API application acting as a server for this and other apps that reside on the same Windows network.
All apps would have a Client Key in form of Guid by which the Web API app can get them authenticated. There is a lot of examples on how to implement a scenario when the end user is getting authenticated by entering credentials in the UI or by implementing an Authentication Server between the app and Web API.
I'm wondering if there is a way to allow users of the app to receive a response seamlessly without entering credentials or being redirected to Authentication Server?
Not sure but I guess I'm wanting to have a class that generates JSON Web Tokens and is used in data annotation on server's action methods like [ValidateAntiForgeryToken]
is used to establish secure communication between browser and server.
Any ideas will be much appreciated.
c# jwt
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12
add a comment |
I'm trying to implement JWT mechanism to secure communication between the .NET MVC application and Web API application acting as a server for this and other apps that reside on the same Windows network.
All apps would have a Client Key in form of Guid by which the Web API app can get them authenticated. There is a lot of examples on how to implement a scenario when the end user is getting authenticated by entering credentials in the UI or by implementing an Authentication Server between the app and Web API.
I'm wondering if there is a way to allow users of the app to receive a response seamlessly without entering credentials or being redirected to Authentication Server?
Not sure but I guess I'm wanting to have a class that generates JSON Web Tokens and is used in data annotation on server's action methods like [ValidateAntiForgeryToken]
is used to establish secure communication between browser and server.
Any ideas will be much appreciated.
c# jwt
I'm trying to implement JWT mechanism to secure communication between the .NET MVC application and Web API application acting as a server for this and other apps that reside on the same Windows network.
All apps would have a Client Key in form of Guid by which the Web API app can get them authenticated. There is a lot of examples on how to implement a scenario when the end user is getting authenticated by entering credentials in the UI or by implementing an Authentication Server between the app and Web API.
I'm wondering if there is a way to allow users of the app to receive a response seamlessly without entering credentials or being redirected to Authentication Server?
Not sure but I guess I'm wanting to have a class that generates JSON Web Tokens and is used in data annotation on server's action methods like [ValidateAntiForgeryToken]
is used to establish secure communication between browser and server.
Any ideas will be much appreciated.
c# jwt
c# jwt
edited Nov 13 '18 at 19:48
JNevill
31.5k31544
31.5k31544
asked Nov 13 '18 at 19:46
GGGGGG
32
32
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12
add a comment |
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12
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%2f53288439%2fusing-json-web-token-to-secure-web-api-communication%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%2f53288439%2fusing-json-web-token-to-secure-web-api-communication%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
I think JWT is what you need. One idea is just generate a string as a token in server after user's credentials, and store this token into a db with expiration date, and at client side, store the token in cookies.
– tim
Nov 13 '18 at 20:12