The samples contained in this repo are used to present an end-to-end demo scenario based on a fictitious B2B and multitenant system, named “HealthClinic.biz” that provides different websites, mobile apps, desktop apps, wearable apps, and services running on the latest Microsoft and open technologies aligned with announcements to showcase during the Connect(); 2015 event.
The current published version works with Visual Studio 2015 Update 1 RC bits and ASP.NET 5.0 Beta 8. The final version used at Connect(); 2015 will be published soon.
The WPF Receptionist application doesn't appear to use any kind of security & authentication other than the CurrentPatientId and TenanatId variables hardcoded in the AppSettings class. If I wanted to implement either an old school SQL username and password login, or an OAuth social authentication using OWIN, how would I implement that on the 01_Demos_ASP.NET side of things? Shouldn't the Receptionist be using an ASPNetUserRole admin role instead of a patient (CurrentPatientId) id?
ibonilm
commented
8 years ago
The WPF Receptionist application doesn't appear to use any kind of security & authentication other than the CurrentPatientId and TenanatId variables hardcoded in the AppSettings class. If I wanted to implement either an old school SQL username and password login, or an OAuth social authentication using OWIN, how would I implement that on the 01_Demos_ASP.NET side of things? Shouldn't the Receptionist be using an ASPNetUserRole admin role instead of a patient (CurrentPatientId) id?