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.

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

[Feature] Multi Factor Auth #45

Open
3 tasks
lenaxia opened this issue Jan 26, 2023 · 1 comment
Open
3 tasks

[Feature] Multi Factor Auth #45

lenaxia opened this issue Jan 26, 2023 · 1 comment

Comments

@lenaxia
Copy link

lenaxia commented Jan 26, 2023

What is this

Feature request for multi factor authentication. Considering this is storing private health data it is important that it be as secure as possible.

Why is this needed?

Ideally MFA would be handled by an external authentication provider such as OIDC or Forward Authentication (preferred). However, in order to develop a zero knowledge model, Fasten would require a user-inputted secret, which neither OIDC and Forward Auth make available.

Hence, the MFA burden falls on the app itself. This is a similar problem to what BitWarden/VaultWarden face with their zero knowledge model.

Implementation

Lots of options out there, but I would personally request support for the following modes:

  • Duo.com
  • TOTP
  • WebAuthn

I specifically request that email and SMS 2nd factor not be supported because of how insecure they are.

When is this needed?

Not now. This is obviously an advanced feature and other core features are higher priority in order to deliver basic functionality.

@AnalogJ
Copy link
Member

AnalogJ commented Aug 22, 2023

related #50

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

No branches or pull requests

2 participants