goauthentik / goauthentik/authentik
Resend and retry for email and SMS authentication codes
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 659
Description
## What
resend/retry for code-based authenticators: SMS send failure cannot retry; email OTP needs an explicit resend and a warning that the previous code is invalid.
## Want
- Resend/retry for code-based authenticators: SMS send failure cannot retry
- Email OTP needs an explicit resend
- A warning that the previous code is invalid
## Ideas this came from
- [#8001 Bug: If SMS sending fails for any reason, user is unable to retry](https://github.com/goauthentik/authentik/issues/8001) — It seems that when using custom SMS API, and Authentik is unable to connect to it or for unknown reasons the SMS is not recieved, user is not able to retry it a
- [#22817 Add option for user to resend email OTP](https://github.com/goauthentik/authentik/issues/22817) — Is your feature request related to a problem? For now when user is asked to type otp from their email client they have no option to resend it other than logging
- [#23123 Email OTP: Clearly notify the user in the UI that the previous OTP code is now invalid](https://github.com/goauthentik/authentik/issues/23123) — Is your feature request related to a problem? When a user requests a new Email OTP code while the previous one is still valid, authentik generates a new token a
Contributor guide
Research direction
Start by reading the three linked issues (#8001, #22817, and #23123) alongside the code-based authenticator flow. Trace how SMS failures and email OTP requests are handled, then verify that users can retry or explicitly resend and are warned when the previous code is invalid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100