[Feature] 2FA (OTP) and Passkeys authentication #799

Closed
opened 2026-02-28 19:20:18 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @giopas on GitHub (Dec 6, 2023).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Although there are other ways to achieve this[1], given the high confidentiality of financial data contained unto ActualBudget, it would be great to be able to implement 2FA (OTP) and/or Passkeys authentication within ActualBudget.

[1] e.g. Authelia

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @giopas on GitHub (Dec 6, 2023). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Although there are other ways to achieve this[1], given the high confidentiality of financial data contained unto ActualBudget, it would be great to be able to implement 2FA (OTP) and/or Passkeys authentication *within* ActualBudget. [1] e.g. Authelia ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:20:18 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 6, 2023):

Thanks for sharing your idea!

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Dec 6, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Author
Owner

@ducpham01 commented on GitHub (Apr 14, 2024):

I'm interested and I hope to work on this issue. By any chance this issue would be reopened ?

@ducpham01 commented on GitHub (Apr 14, 2024): I'm interested and I hope to work on this issue. By any chance this issue would be reopened ?
Author
Owner

@yauyenching commented on GitHub (Sep 8, 2024):

i also think 2FA is rather important for sensitive financial data! please consider readding this feature to the pipeline for anyone interested to take up 👍🏻

@yauyenching commented on GitHub (Sep 8, 2024): i also think 2FA is rather important for sensitive financial data! please consider readding this feature to the pipeline for anyone interested to take up 👍🏻
Author
Owner

@StephenBrown2 commented on GitHub (Jan 22, 2026):

Could use https://pocket-id.org/ as your OAuth provider, it only does passkeys.

@StephenBrown2 commented on GitHub (Jan 22, 2026): Could use https://pocket-id.org/ as your OAuth provider, it only does passkeys.
Author
Owner

@db-src commented on GitHub (Jan 22, 2026):

please consider readding this feature to the pipeline for anyone interested to take up

As the automated reply states, there is no "pipeline" or assignment of tasks, rather the maintainers may take votes into account when they find spare time, and/or other contributors can submit pull requests any time. So this issue doesn't need reopened or anything, and if someone wants to do it, just research and make a PR.

@db-src commented on GitHub (Jan 22, 2026): > please consider readding this feature to the pipeline for anyone interested to take up As the automated reply states, there is no "pipeline" or assignment of tasks, rather the maintainers may take votes into account when they find spare time, and/or other contributors can submit pull requests any time. So this issue doesn't need reopened or anything, and if someone wants to do it, just research and make a PR.
Author
Owner

@damianon commented on GitHub (Feb 16, 2026):

I feel like now with oidc support this feature is somewhat irrelevant, at least to me, since with an oidc provider you could get all kinds of auth options

@damianon commented on GitHub (Feb 16, 2026): I feel like now with oidc support this feature is somewhat irrelevant, at least to me, since with an oidc provider you could get all kinds of auth options
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#799