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







share|improve this 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.



















    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







    share|improve this 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.

















      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







      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      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.































          active

          oldest

          votes






















          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes

          Popular posts from this blog

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d
          Read more

          SQL update select statement

          Image
          0 I'm trying to update an entry in my database (postgresql). I'm having a problem with updating the query: INSERT INTO prices (price, product_id) SELECT product_price, commn_id FROM products_temp as prod WHERE NOT EXISTS (SELECT * FROM prices od WHERE prod.commn_id = od.product_id) OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) Query works fine when i delete: OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) So it seems to me that it's looping through this operation. My question is, how can I fix it? sql postgresql
          Read more

          WPF add header to Image with URL pettitions [duplicate]

          Image
          up vote 0 down vote favorite This question already has an answer here: Image source URI requiring authorization 3 answers Add header to all* HTTP requests on a machine 1 answer first of all sorry for my english. Recently I added some security in the backend of my project, and now I need to send a validation code(apiKey) inside the headers to retrieve the images. I have a problem with ALL images in my project that I had attached in my UI. For example, before I had: <Image Height="90" Source="{Binding Video.Thumbnail}"/> Now I need to change my code to create a CUSTOM petition add the apiKey in the header:
          Read more