[Pleroma] 2fa is not working #205

Closed
opened 2021-12-31 09:34:18 +01:00 by darhma · 4 comments

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

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
fede added the
bug
🤔️ Investigate
Akkoma
labels 2022-01-05 21:10:14 +01:00
fede added this to the (deleted) project 2022-01-07 21:40:19 +01:00
muppeth added this to the (deleted) milestone 2022-05-07 08:59:48 +02:00
Owner

@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:

XHR POST https://fe.disroot.org/api/pleroma/accounts/mfa/confirm/totp
[HTTP/1.1 422 Unprocessable Entity 118ms]

I've added

  multi_factor_authentication: [
    totp: [
      # digits 6 or 8
      digits: 6,
      period: 30
    ],
    backup_codes: [
      number: 5,
      length: 16
    ]
  ],

in /etc/akkoma/config.exs as shown here https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/config/config.exs

But it doesn't change anything.

In journalct I see that request_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.

@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: ``` XHR POST https://fe.disroot.org/api/pleroma/accounts/mfa/confirm/totp [HTTP/1.1 422 Unprocessable Entity 118ms] ``` I've added ``` multi_factor_authentication: [ totp: [ # digits 6 or 8 digits: 6, period: 30 ], backup_codes: [ number: 5, length: 16 ] ], ``` in `/etc/akkoma/config.exs` as shown here https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/config/config.exs But it doesn't change anything. In `journalct` I see that `request_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.
meaz added this to the 23.03 - March milestone 2023-02-25 08:43:08 +01:00
Owner
I've created an issue there https://akkoma.dev/AkkomaGang/akkoma/issues/490
muppeth added this to the 23.03 - March project 2023-03-08 12:13:11 +01:00
Owner

@muppeth I've just deployed our role on vagrant: I don't have that issue. So yeah, must be coming from ldap...

@muppeth I've just deployed our role on vagrant: I don't have that issue. So yeah, must be coming from ldap...
meaz added the
ldap
label 2023-03-16 22:06:35 +01:00
muppeth removed this from the 23.03 - March milestone 2023-04-05 19:51:00 +02:00
muppeth removed this from the 23.03 - March project 2023-04-10 12:21:12 +02:00
Owner

I think it's the same as #213 which has progressed so we can close this one.

I think it's the same as #213 which has progressed so we can close this one.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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: Disroot/Disroot-Project#205
No description provided.