Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

complete authentication #27

Open
hohwille opened this issue Sep 3, 2019 · 0 comments
Open

complete authentication #27

hohwille opened this issue Sep 3, 2019 · 0 comments

Comments

@hohwille
Copy link
Member

hohwille commented Sep 3, 2019 •
edited
Loading

  • currently I can not see who I am after being logged in. This is IMHO a generic requirement of any app.
  • currently there seems no way to log out
  • I personally want to ask if we should do the authentication by the backend. What if I want to use the REST API without the client? You might have arguments against this point and I am open for discussion. The authentication scheme is provided by the backend. So shouldnt the backend be fully responsible then? If we change or extend the authentication (e.g. add TFA via TOTP or switch to FIDO2) shoud we always change the client? What if we have multiple clients (angular, Android, iOS, etc.)? Should be be forced to change all of them? Or would it be better to have a design where only the backend is in charge of controling the login process?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hohwille