Authentication in Web API project using the session that is from ASP.NET Web Forms project
I know it is bad and not recommended, but unfortunately, I am dealing with a legacy product and has limited permissions to make reasonable changes to avoid this.
In my solution, I have an ASP.NET Web Forms website, and I have recently added a new ASP.NET Web API project.
The Web Forms website is session and cookie based (HttpContext.Current.Session).
I have to stick in a single page React app into a page inside Web Forms. The requirement for the React app is to use a separate ASP.NET Web API based endpoints while using the current authentication available in ASP.NET Web Forms.
The react is able to access the local cookie, and there is no problem with organizing the project itself, placing js files etc.
The only problem is - how do I authorize the requests made from React to the Web API? I have to use ASP.NET Web Forms session.
Thanks for the guidance.
c# asp.net asp.net-web-api webforms asp.net-web-api2
add a comment |
I know it is bad and not recommended, but unfortunately, I am dealing with a legacy product and has limited permissions to make reasonable changes to avoid this.
In my solution, I have an ASP.NET Web Forms website, and I have recently added a new ASP.NET Web API project.
The Web Forms website is session and cookie based (HttpContext.Current.Session).
I have to stick in a single page React app into a page inside Web Forms. The requirement for the React app is to use a separate ASP.NET Web API based endpoints while using the current authentication available in ASP.NET Web Forms.
The react is able to access the local cookie, and there is no problem with organizing the project itself, placing js files etc.
The only problem is - how do I authorize the requests made from React to the Web API? I have to use ASP.NET Web Forms session.
Thanks for the guidance.
c# asp.net asp.net-web-api webforms asp.net-web-api2
add a comment |
I know it is bad and not recommended, but unfortunately, I am dealing with a legacy product and has limited permissions to make reasonable changes to avoid this.
In my solution, I have an ASP.NET Web Forms website, and I have recently added a new ASP.NET Web API project.
The Web Forms website is session and cookie based (HttpContext.Current.Session).
I have to stick in a single page React app into a page inside Web Forms. The requirement for the React app is to use a separate ASP.NET Web API based endpoints while using the current authentication available in ASP.NET Web Forms.
The react is able to access the local cookie, and there is no problem with organizing the project itself, placing js files etc.
The only problem is - how do I authorize the requests made from React to the Web API? I have to use ASP.NET Web Forms session.
Thanks for the guidance.
c# asp.net asp.net-web-api webforms asp.net-web-api2
I know it is bad and not recommended, but unfortunately, I am dealing with a legacy product and has limited permissions to make reasonable changes to avoid this.
In my solution, I have an ASP.NET Web Forms website, and I have recently added a new ASP.NET Web API project.
The Web Forms website is session and cookie based (HttpContext.Current.Session).
I have to stick in a single page React app into a page inside Web Forms. The requirement for the React app is to use a separate ASP.NET Web API based endpoints while using the current authentication available in ASP.NET Web Forms.
The react is able to access the local cookie, and there is no problem with organizing the project itself, placing js files etc.
The only problem is - how do I authorize the requests made from React to the Web API? I have to use ASP.NET Web Forms session.
Thanks for the guidance.
c# asp.net asp.net-web-api webforms asp.net-web-api2
c# asp.net asp.net-web-api webforms asp.net-web-api2
asked Nov 19 '18 at 21:47
IlhamIlham
60615
60615
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Have your React app use the cookie when sending a request to the Web API (either in the header if the domain names allow, or make a special authentication call were you send the content of the cookie in the body of the HTTP request to the API).
Then your Web API can make an HTTP request to the ASP.NET app with the cookie. If it gets back anything but a 401, then you known the cookie is good.
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%2f53383112%2fauthentication-in-web-api-project-using-the-session-that-is-from-asp-net-web-for%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
Have your React app use the cookie when sending a request to the Web API (either in the header if the domain names allow, or make a special authentication call were you send the content of the cookie in the body of the HTTP request to the API).
Then your Web API can make an HTTP request to the ASP.NET app with the cookie. If it gets back anything but a 401, then you known the cookie is good.
add a comment |
Have your React app use the cookie when sending a request to the Web API (either in the header if the domain names allow, or make a special authentication call were you send the content of the cookie in the body of the HTTP request to the API).
Then your Web API can make an HTTP request to the ASP.NET app with the cookie. If it gets back anything but a 401, then you known the cookie is good.
add a comment |
Have your React app use the cookie when sending a request to the Web API (either in the header if the domain names allow, or make a special authentication call were you send the content of the cookie in the body of the HTTP request to the API).
Then your Web API can make an HTTP request to the ASP.NET app with the cookie. If it gets back anything but a 401, then you known the cookie is good.
Have your React app use the cookie when sending a request to the Web API (either in the header if the domain names allow, or make a special authentication call were you send the content of the cookie in the body of the HTTP request to the API).
Then your Web API can make an HTTP request to the ASP.NET app with the cookie. If it gets back anything but a 401, then you known the cookie is good.
answered Nov 19 '18 at 22:25
Gabriel LuciGabriel Luci
10.5k11424
10.5k11424
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%2f53383112%2fauthentication-in-web-api-project-using-the-session-that-is-from-asp-net-web-for%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