Codeberg/Community
54
325
Fork
You've already forked Community
12

2FA setup doesn’t clearly prompt users to save their recovery code #1842

Open
opened 2025年04月06日 09:53:30 +02:00 by ehucke · 1 comment

Comment

After enabling 2FA on Codeberg, users are redirected to the Account Security page. At the top, there’s a green banner displaying the recovery code with a note saying it should be saved.

There are a couple of problems with this:

  1. It's easy to overlook. Most platforms include an explicit confirmation step here — like requiring the user to check a box confirming they’ve saved the recovery code, or offering a download link (PDF or TXT). These extra steps help ensure the code actually gets saved, which is kind of the whole point.

  2. The green banner feels misleading. Green usually signals success or completion, so many users will assume this is just a confirmation that 2FA was set up properly and may not realize there's still something important they need to do.

Suggestions:

  • Add a confirmation step in the 2FA setup process that makes the user acknowledge they've saved the recovery code.
  • Include a download option for the code (PDF or TXT).
  • (Not needed if adding the recovery code as an additional confirmation step) Consider changing the visual style of the banner — something more neutral or attention-grabbing would make the message stand out better and clarify that there’s still an action required.
### Comment After enabling 2FA on Codeberg, users are redirected to the Account Security page. At the top, there’s a green banner displaying the recovery code with a note saying it should be saved. There are a couple of problems with this: 1. It's easy to overlook. Most platforms include an explicit confirmation step here — like requiring the user to check a box confirming they’ve saved the recovery code, or offering a download link (PDF or TXT). These extra steps help ensure the code actually gets saved, which is kind of the whole point. 2. The green banner feels misleading. Green usually signals success or completion, so many users will assume this is just a confirmation that 2FA was set up properly and may not realize there's still something important they need to do. ### Suggestions: - Add a confirmation step in the 2FA setup process that makes the user acknowledge they've saved the recovery code. - Include a download option for the code (PDF or TXT). - (Not needed if adding the recovery code as an additional confirmation step) Consider changing the visual style of the banner — something more neutral or attention-grabbing would make the message stand out better and clarify that there’s still an action required.

It's indeed pretty bad. Consider moving this to Forgejo issue tracker, it affects all instances
https://codeberg.org/forgejo/forgejo/issues

It's indeed pretty bad. Consider moving this to Forgejo issue tracker, it affects all instances https://codeberg.org/forgejo/forgejo/issues
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1842
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?