#336 [discussion] scratch token UX

Open
opened 2 weeks ago by tkgroot · 2 comments
tkgroot commented 2 weeks ago

Its easy to overlook the scratch token if presented after enrolling 2FA. I find it to subtle presented and easy to miss.

A modal/popover or something more "in ya face" might be better to not forget to store that key, since its important. Even the opportunity to block users to proceed without having at least stored it to the clipboard, might be an option here.

Its easy to overlook the scratch token if presented after enrolling 2FA. I find it to subtle presented and easy to miss. A modal/popover or something more "in ya face" might be better to not forget to store that key, since its important. Even the opportunity to block users to proceed without having at least stored it to the clipboard, might be an option here.
hw added the
gitea-related issue
label 2 weeks ago
hw added the
enhancement
label 2 weeks ago
hw commented 2 weeks ago
Poster
Owner

This seems best implemented within gitea, would you like to create an upstream issue in the gitea issue tracker?

This seems best implemented within gitea, would you like to create an upstream issue in the gitea issue tracker?
tkgroot commented 2 weeks ago
Poster

Sure. for the sake of completion gitea issue #13600

Sure. for the sake of completion [gitea issue #13600](https://github.com/go-gitea/gitea/issues/13600)
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.