You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: