[Pleroma] 2fa is not working #205
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#205
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?
On the fe.disroot.org instance if I try to activate the 2fa it makes me do all the procedure and it should be activated, but if I log out and then try to log in again it doesn't ask for the 2fa and if I go in the settings it doesn't result active
@muppeth I've done some tests now that we use Akkoma.
To set 2fa, you have to go there: https://fe.disroot.org/settings/mfa
It will create recovery codes. Then, you can set up 2fa.
When done, you're being asked to verify everything, so you have to enter code and password. When you press Confirm, you get a message
Incorrect code or password. Try again.
even though everything is set up correctly.In firefox console I see this:
I've added
in
/etc/akkoma/config.exs
as shown here https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/config/config.exsBut it doesn't change anything.
In
journalct
I see thatrequest_id=POE2EA3JIEfmq90AAHKC [error] Password hash not recognized
though my password is right, as I'm able to log in fe.disroot.org without any problem.I've created an issue there https://akkoma.dev/AkkomaGang/akkoma/issues/490
@muppeth I've just deployed our role on vagrant: I don't have that issue. So yeah, must be coming from ldap...
I think it's the same as #213 which has progressed so we can close this one.