Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

WPF Receptionist App Security? #14

Open
Onjay opened this issue Jun 20, 2016 · 1 comment
Open

WPF Receptionist App Security? #14

Onjay opened this issue Jun 20, 2016 · 1 comment

Comments

@Onjay
Copy link

Onjay commented Jun 20, 2016

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
Copy link
Contributor

ibonilm commented Jun 21, 2016

The REST API that this app uses is not authenticated, it´s a demo app that was not focused on this area. Sorry.

Of course, you could modify the app to add the authentication system that you prefer. Now, the backoffice uses ASP.NET Identity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants