Mixing
Design of Azure Web Service/ API / Mobile App [on hold]
up vote
0
down vote
favorite
I have an ASP.NET CORE MVC WebApp with Identity framework. Now that we are also planning to extend our product such that we can provide mobile apps with xamerin, I decided to make an API so that we don't have to code the backend twice. We currently host our App in the Azure Cloud.
1) For the backend: I would like to use ASP.NET CORE WebApi but I figured that there is no such Identity template nor a native Azure Web API integration. So would it be better to use ASP.NET instead?
2) Since I authenticated the ASP.NET Core MVC Web App via identity framework, I would like to also use that in the backend. So that you log in on the backend and receive a token, once you logged in successfully. I have to code to login the user at the backend and return a token. How exactly can I authenticate the .NET ASP CORE Frontend? The user will query the login page -> AuthConntroller.Login-> Login method starts a call to Login Backend API -> Backend API queries backend-database -> if successful return true-> backend generates a token->sends it back to frontend-> frontend uses Owin so that I can use the [Authorize] Attribute in the controller classes so that I can authenticate the user?
3) Mobile and Desktop requirements are pretty different (or may become?). Since that could become a problem later on, I thought about creating a basic API for the most common database queries and another two that inherit from the first and extend it to mobile and desktop needs. So at some point, I would have two API's. Is that a good approach? Any thoughts or resources that you can recommend about that?
3) I'm using MySQL currently. What are the downside of MS SQL? Should I swich to MS SQL when using the identity framework since the entire structure of Identity Core is designed around MS?
Anything else that I have to consider when I'm using such an API design?
Thank you so much for any hints/tricks/links/recommendations on my dilemma.
Sincerely,
Paul
asp.net asp.net-core asp.net-core-mvc azure-web-app-service asp.net-core-identity
asked 4 hours ago
PauLy
394
put on hold as too broad by Knelis, Stephen Muecke, Peter B, Joy Wang, Dalija Prasnikar 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I have an ASP.NET CORE MVC WebApp with Identity framework. Now that we are also planning to extend our product such that we can provide mobile apps with xamerin, I decided to make an API so that we don't have to code the backend twice. We currently host our App in the Azure Cloud.
1) For the backend: I would like to use ASP.NET CORE WebApi but I figured that there is no such Identity template nor a native Azure Web API integration. So would it be better to use ASP.NET instead?
2) Since I authenticated the ASP.NET Core MVC Web App via identity framework, I would like to also use that in the backend. So that you log in on the backend and receive a token, once you logged in successfully. I have to code to login the user at the backend and return a token. How exactly can I authenticate the .NET ASP CORE Frontend? The user will query the login page -> AuthConntroller.Login-> Login method starts a call to Login Backend API -> Backend API queries backend-database -> if successful return true-> backend generates a token->sends it back to frontend-> frontend uses Owin so that I can use the [Authorize] Attribute in the controller classes so that I can authenticate the user?
3) Mobile and Desktop requirements are pretty different (or may become?). Since that could become a problem later on, I thought about creating a basic API for the most common database queries and another two that inherit from the first and extend it to mobile and desktop needs. So at some point, I would have two API's. Is that a good approach? Any thoughts or resources that you can recommend about that?
3) I'm using MySQL currently. What are the downside of MS SQL? Should I swich to MS SQL when using the identity framework since the entire structure of Identity Core is designed around MS?
Anything else that I have to consider when I'm using such an API design?
Thank you so much for any hints/tricks/links/recommendations on my dilemma.
Sincerely,
Paul
asp.net asp.net-core asp.net-core-mvc azure-web-app-service asp.net-core-identity
asked 4 hours ago
PauLy
394
put on hold as too broad by Knelis, Stephen Muecke, Peter B, Joy Wang, Dalija Prasnikar 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an ASP.NET CORE MVC WebApp with Identity framework. Now that we are also planning to extend our product such that we can provide mobile apps with xamerin, I decided to make an API so that we don't have to code the backend twice. We currently host our App in the Azure Cloud.
1) For the backend: I would like to use ASP.NET CORE WebApi but I figured that there is no such Identity template nor a native Azure Web API integration. So would it be better to use ASP.NET instead?
2) Since I authenticated the ASP.NET Core MVC Web App via identity framework, I would like to also use that in the backend. So that you log in on the backend and receive a token, once you logged in successfully. I have to code to login the user at the backend and return a token. How exactly can I authenticate the .NET ASP CORE Frontend? The user will query the login page -> AuthConntroller.Login-> Login method starts a call to Login Backend API -> Backend API queries backend-database -> if successful return true-> backend generates a token->sends it back to frontend-> frontend uses Owin so that I can use the [Authorize] Attribute in the controller classes so that I can authenticate the user?
3) Mobile and Desktop requirements are pretty different (or may become?). Since that could become a problem later on, I thought about creating a basic API for the most common database queries and another two that inherit from the first and extend it to mobile and desktop needs. So at some point, I would have two API's. Is that a good approach? Any thoughts or resources that you can recommend about that?
3) I'm using MySQL currently. What are the downside of MS SQL? Should I swich to MS SQL when using the identity framework since the entire structure of Identity Core is designed around MS?
Anything else that I have to consider when I'm using such an API design?
Thank you so much for any hints/tricks/links/recommendations on my dilemma.
Sincerely,
Paul
asp.net asp.net-core asp.net-core-mvc azure-web-app-service asp.net-core-identity
asked 4 hours ago
PauLy
394
I have an ASP.NET CORE MVC WebApp with Identity framework. Now that we are also planning to extend our product such that we can provide mobile apps with xamerin, I decided to make an API so that we don't have to code the backend twice. We currently host our App in the Azure Cloud.
1) For the backend: I would like to use ASP.NET CORE WebApi but I figured that there is no such Identity template nor a native Azure Web API integration. So would it be better to use ASP.NET instead?
2) Since I authenticated the ASP.NET Core MVC Web App via identity framework, I would like to also use that in the backend. So that you log in on the backend and receive a token, once you logged in successfully. I have to code to login the user at the backend and return a token. How exactly can I authenticate the .NET ASP CORE Frontend? The user will query the login page -> AuthConntroller.Login-> Login method starts a call to Login Backend API -> Backend API queries backend-database -> if successful return true-> backend generates a token->sends it back to frontend-> frontend uses Owin so that I can use the [Authorize] Attribute in the controller classes so that I can authenticate the user?
3) Mobile and Desktop requirements are pretty different (or may become?). Since that could become a problem later on, I thought about creating a basic API for the most common database queries and another two that inherit from the first and extend it to mobile and desktop needs. So at some point, I would have two API's. Is that a good approach? Any thoughts or resources that you can recommend about that?
3) I'm using MySQL currently. What are the downside of MS SQL? Should I swich to MS SQL when using the identity framework since the entire structure of Identity Core is designed around MS?
Anything else that I have to consider when I'm using such an API design?
Thank you so much for any hints/tricks/links/recommendations on my dilemma.
Sincerely,
Paul
asp.net asp.net-core asp.net-core-mvc azure-web-app-service asp.net-core-identity
asp.net asp.net-core asp.net-core-mvc azure-web-app-service asp.net-core-identity
asked 4 hours ago
PauLy
394
asked 4 hours ago
PauLy
394
asked 4 hours ago
PauLy
394
asked 4 hours ago
PauLy
394
asked 4 hours ago
PauLy
394
394
put on hold as too broad by Knelis, Stephen Muecke, Peter B, Joy Wang, Dalija Prasnikar 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by Knelis, Stephen Muecke, Peter B, Joy Wang, Dalija Prasnikar 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
