I have a question about the architecture of my IdendityProvider for User authentication. For security, I would divide my frontend exposed on the internet from backed that is internal to my network behind my firewall, and communicate through REST API. I would use AspNet Core Identity for both sides. It's a good idea or not? If it is a bad idea what kind of architecture can I adopt in this scenario? Below the simple picture of architecture. My hypothetical achitecture

Thanks a lot

  • so your FE server passes the users token to the BE server? – Ewan Dec 5 '19 at 16:52
  • how does the FE verify the user without a user DB? – Ewan Dec 5 '19 at 16:54
  • The FE does not have a logic, it only shows the screens to perform the Login, the Recovery Password, etc. All logic and user management are on the BE. FE only sends requests to BE via the REST API. – pampua84 Dec 9 '19 at 11:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.