[Lemmy] Update TOTP (2FA) Setup to present secret key. #776
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#776
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
During TOTP(2FA) setup, a "secret key' text should be displayed and available to use for when scanning of a QR code is not available.
I was able to, first, use the link in the lower section and utilize a native authenticator. However, within KeepasXC, there is no operability with that portion and also cannot read QR codes. I was able to utilize a separate QR code scanner with reads a very long QR code value and I was able to identify and use the secret key portion in order to set up the TOTP option inside KeepassXC.
@Shadowstreik what happens when you click on "2FA installation link"?
That isssue should be better reported on lemmy UI repo: https://github.com/LemmyNet/lemmy-ui/
@meaz If an authenticator app is installed on the PC, it attempts to open it and begin the setup. On my Linux Mint Debian Edition build, it does have an authenticator app included, natively. However, I use KeepassXC, with requires a text-based key in order to set up TOTP; it cannot read QR codes.
My thoughts were Lemmy has a toggle to enable the text-based key to use on the admin panel. If that's not the case, say so and I'll gladly head over to GitHub and report the issue, there.
I'm not sure if I understand the issue, @Shadowstreik
I was able to config the TOTP in my KeePassXC with the installation link provided by Lemmy. Yes, it has to be manually done, but I had no issues.
I click on the Link button in Scribe and Authenticator opens up. The expected behavior is to have the Secret Key text displayed within Lemmy to allow Copy & Paste into KeePassXC (I'm on version 2.7.6) which cannot read QR codes.
The first image is inside Lemmy and does not display a Secret Key to copy and paste into the KeePassXC TOTP setup("Setup TOTP" pic). Clicking on the link button opens the native Authenticator app in LMDE. Some folks may not have an already installed authenticator app to obtain the key from and end up confused on how to proceed.
@Shadowstreik I've checked, this is how this is implemented, I can not change this. That means you have to report that to Lemmy devs.
Understood. Thank you for looking and will do! :D
UPDATE
There, already a ticket in over on GitHub. It's been there since last Summer. Considering the tags placed on the report, one would think it would have, already, been addressed.
https://github.com/LemmyNet/lemmy-ui/issues/1863